You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add support to mcpd search with a flag (--format) for outputting search results in json, yaml or plain text.
* Tweak: Don't print Name in text results of search.
* Change: JSON field names adjusted to use snake_case instead of camelCase.
* Tidied up mcpd config export long description.
return`Exports current configuration, generating a pair of safe and portable configuration files.
71
+
72
+
Using a project's required configuration (e.g. .mcpd.toml) and the locally configured runtime values from the execution context file (e.g. ~/.config/mcpd/secrets.dev.toml), the export command outputs two files:
73
+
74
+
Environment Contract:
75
+
- Lists all required and configured environment variables as secure, namespaced placeholders
76
+
e.g. MCPD__{SERVER_NAME}__{ENV_VAR}
77
+
- Creates placeholders for command line arguments to be populated with env vars
78
+
e.g. MCPD__{SERVER_NAME}__ARG_{ARG_NAME}
79
+
- This file is intended for the platform operator or CI/CD system
80
+
81
+
Portable Execution Context:
82
+
- A new secrets .toml file that defines sanitized runtime args and env sections for each server using the placeholders aligned with the environment contract
83
+
- These files are safe to check into version control if required.
84
+
85
+
"This allows running an mcpd project in any environment, cleanly separating the configuration structure from the secret values`
0 commit comments