MCP Integration

MCP servers add external tools to Anyy. Each server belongs to one Profile, is probed to discover its catalog, and exposes only the tools you explicitly select.

Anyy supports local stdio servers and remote HTTP servers, including supported OAuth and header authentication.

Recommended Setup Flow

1. Add the server without broad tool exposure.
2. Probe the connection and discover its catalog.
3. Review every tool you intend to expose.
4. Include only the tools you need.
5. Enable the server and activate its toolset.

An MCP server is a trust boundary

It can receive tool inputs, return content to the model, and—for local processes—run with the operating-system access of the Anyy runtime. Review the operator, package or command, transport, authentication, and tool behavior.

Add a Server in Dashboard

Open Dashboard → MCP → Add MCP server.

1. Enter a stable Server ID.
2. Choose stdio for a local command or http for a remote endpoint.
3. Enter the executable and arguments, or the MCP URL.
4. Configure authentication, headers, environment values, and secret references.
5. Select Probe to connect and discover the catalog.
6. Add allowed tools to Included tools and deny additional names with Excluded tools.
7. Optionally enable the server and activate its toolset for new sessions.
8. Submit and approve the ChangePlan.

An enabled draft requires a successful probe matching the current form and an explicit include list. Editing connection or policy fields after probing invalidates that evidence; probe again before saving.

Start with read-only tools

Expose the smallest catalog that completes the task. Add write or delete tools only after reviewing their effects and Anyy's effective governance.

Local stdio Servers

Anyy launches a local executable and communicates through standard input/output. Configure its command, one argument per line, environment values, and protected secret references.

CLI example:

anyy mcp add context \
  --transport stdio \
  --command npx \
  --args -y @upstash/context7-mcp

Pin or review the package or executable. Do not place raw credentials in ordinary environment configuration when the field supports a protected secret reference.

Remote HTTP Servers

anyy mcp add remote-docs \
  --url https://mcp.example.com \
  --transport http \
  --auth oauth

Remote authentication modes are:

• oauth;
• header; and
• none.

Use HTTPS and keep authorization values out of URLs. Choose none only for an intentionally unauthenticated endpoint.

For OAuth, complete login after adding the server:

anyy mcp login remote-docs

Log in again if the server reports reauth_needed. Removing a server also removes Anyy-managed OAuth credentials after confirmation.

Discover and Scope Tools

Inspect and probe one server:

anyy mcp show context
anyy mcp probe context
anyy mcp test context

Then select tools and activate its toolset:

anyy mcp configure context \
  --include resolve-library-id,get-library-docs \
  --enable \
  --activate-toolset

Tool names come from discovery. Included tools is the allowlist; Excluded tools removes a name even if another selection would include it. Existing sessions may need to be replaced after toolset activation.

MCP configuration does not override Anyy's hard governance floor. Risk, approval policy, timeout, and output budgets remain effective for each materialized tool.

Read Runtime Status

Dashboard separates intended configuration from observed availability:

• Setting enabled/disabled — whether the Profile intends to use the server;
• available/unavailable/pending/degraded — whether it is currently usable; and
• running — whether a client connection is active.

Open a server to inspect its latest probe, allowed tool count, runtime definitions, diagnostic events, and edit form.

Operate and Diagnose

anyy mcp list
anyy mcp status
anyy mcp logs context
anyy mcp reload context

Add --json to supported status and automation-oriented commands when another program needs structured output.

Call one tool directly for a controlled test:

anyy mcp call context.resolve-library-id \
  --args '{"libraryName":"docusaurus"}'

Direct calls use the tool's JSON schema and retain its effective risk and audit behavior.

Disable or Remove

anyy mcp disable context
anyy mcp remove context

Disabling preserves configuration while removing the server from active use. Removing deletes its configured entry; use --force only when normal safety checks cannot complete and you understand the consequence.

Security Checklist

• Pin or review local packages and commands.
• Use HTTPS for remote servers.
• Store credentials through secret references.
• Include only required tools.
• Probe again after command, URL, authentication, or tool-policy changes.
• Review high-risk MCP ChangePlans before approval.

Troubleshooting

Problem	Fix
Local server never starts	Run its exact command manually and verify executable, arguments, and environment
Remote server is unauthorized	Check auth mode, OAuth state, or protected header value
Save is rejected	Probe the current draft and select at least one included tool
Server remains unavailable	Inspect logs and run anyy mcp test SERVER_ID
Tools are discovered but missing in Chat	Include them, enable and activate the toolset, reload, and start a new session
Tool schema changed	Probe again, review the catalog, and update the include list

See Tools & Toolsets and Approvals & ChangePlans for effective governance and review.