MCP servers

MCP (Model Context Protocol) servers connect agents to tools and data sources. In VisuAgent Manager they are first-class Library items with enablement, environment variables, and broad agent coverage.

Purpose

• Define local (command/stdio) or remote (URL) servers once
• Assign them to Global and/or Workspace destinations for compatible agents
• Enable or disable a server without deleting its Library definition
• Keep sensitive credentials out of portable Library files

Create or import

Create

1. Open Library → MCP Servers → New.
2. Set the name and transport (local command vs remote URL as the form allows).
3. Provide platform command details where required (for example macOS/Linux/Windows command overrides).
4. Add environment variables; mark secrets as Sensitive.
5. Save.

Import

Run synchronization against enabled agents. External MCP entries can appear in review with a default action of Import. Matching Library items may auto-link instead of duplicating.

Environment values and sensitive data

• Non-sensitive env values travel with the Library item files and are suitable for shared, non-secret configuration.
• Sensitive values are encrypted for local use and excluded from portable Library files.
• When you move a Library to another computer, re-enter sensitive values and mark them Sensitive again before sharing.
• Sync may warn when sensitive env handling needs attention.

See Data and security for storage expectations.

Compatibility

MCP is the most widely supported feature, but scope still varies:

• Many agents support both Global and Workspace MCP (Claude Code, Codex, Cursor, OpenCode, and others).
• Some support Global only or mark Workspace as gated/unverified (Cline, GitHub Copilot CLI, Hermes, Devin project MCP, etc.).
• Remote URL transports are agent-specific; local stdio is the common baseline.

Always trust assignment UI exclusions and the Supported agents matrix over assumptions.

Enablement and synchronization

1. Assign the server to Global or a Workspace for target agents.
2. Ensure the item is enabled if you want it present in agent config.
3. With live updates on, assignment writes promptly; otherwise run Sync.
4. Disabled managed servers can be removed from agent configs during review/auto-apply paths.

Troubleshooting pointers

Symptom	What to try
Server missing from agent	Confirm agent enabled, feature/scope supported, item assigned and enabled, then sync
Sensitive values missing after copy	Re-enter secrets on the new machine; they are not portable
Remote server fails on one agent	Agent may only support local stdio or a different remote schema
Duplicate imports	Prefer linking matches over repeated Import decisions

More steps: Troubleshooting.