Secret Store

Copy secrets between environments

copy_environment

Copy secrets from one environment of a project to another without the values passing through you (they are re-encrypted on the server). Requires secrets:read on the source, secrets:write on the target and the editor role. Protected secrets are skipped.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "copy_environment"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Target environment
`from`	Yes	Source environment
`keys`	No	Only these keys (default: all)
`project`	Yes	Project slug or id
`overwrite`	No	Replace keys that already exist in the target

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds real behavior beyond the annotations: values never pass through the caller, re-encryption happens server-side, and protected secrets are silently skipped. It still leaves open what a partial copy looks like when target keys exist and overwrite is false, which matters because key collisions silently drop entries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and scope, with the security model and permission requirements packed into the same sentence rather than padded out. No redundant restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers permissions, mutation semantics, and skip behavior for a 5-parameter write tool with no output schema. It could go slightly further by saying what the call reports back (which keys copied versus skipped), since no output schema exists to carry that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so from/to/project/keys/overwrite are already documented in the schema. The description adds no parameter-level meaning beyond that baseline, mentioning neither the 500-key limit nor the interaction between existing keys and overwrite.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Copy secrets from one environment ... to another') plus the scope qualifier 'of a project', so the agent knows exactly what moves. It does not name a sibling such as diff_environments or import_env to contrast against, so differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete preconditions (secrets:read on source, secrets:write on target, editor role) that effectively tell the agent when the call will succeed. There is no explicit statement of when to prefer this over import_env, pull_env, or diff_environments, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Secret Store tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?