Kucedr supports Model Context Protocol, an open standard for connecting external tools and data to AI assistants, over remote HTTP and local stdio transports.
| Transport | Configuration |
|---|---|
| Remote HTTP | Server ID, name, URL, optional bearer token, optional OAuth client ID and client secret. |
| Local stdio | Server ID, name, command, whitespace-split arguments, optional KEY=value environment variables, optional working directory. |
Configure A Server
MCP settings provide one unified list for remote services, configured commands, and discovered local packages. You can add or edit a server, enable or disable it, inspect registry and connection diagnostics, run a live test with tool count and latency, and authorize or reauthorize OAuth for an HTTP server without a bearer token.
The server ID and transport type cannot be changed after creation. The detail view supports configuration, testing, and removal. It also shows the ID, status, URL or command, authentication type, creation and update times, and last error.
After a server is authenticated or tested, Kucedr saves its tool catalog locally. Agent runs search those saved definitions without connecting to every server or listing every tool again. When the agent selects a tool, Kucedr connects to its server for execution. Use Test after the server changes its tools to refresh the saved catalog. An enabled server without a saved catalog is listed once in the background after an upgrade.
Local Packages
Kucedr discovers local server packages dynamically from ~/.kucedr/mcp/servers. Place a valid package folder there and read MCP settings or start an agent run to refresh the registry. The current Settings page has no local-package upload, folder-opening, or manual refresh control. You can test a discovered server from its details page.
Each package lives in its own folder and contains an mcp.json manifest:
{
"id": "filesystem",
"name": "Filesystem",
"type": "stdio",
"command": "node",
"args": ["dist/server.js"],
"env": { "MODE": "production" },
"cwd": ".",
"require_approval": "always",
"enabled": true
}
The folder name becomes the ID when id is omitted. IDs use lowercase letters, numbers, and single hyphens. Relative working directories resolve from the package folder. Explicitly configured servers take precedence over a discovered package with the same ID, while malformed or duplicate packages are reported without blocking other servers.
Approval Behavior
The stored require_approval field is enforced. It sets each loaded MCP tool's default permission to Allow or Ask.
MCP tools are not part of Kucedr's built-in gated-tool list, so their own require_approval setting is the applicable default. Review the server, its operator, and every exposed tool before enabling it.
Current Limits
- The stored
defer_loadingfield remains for compatibility; agent runs use the saved catalog regardless of its value. - Dynamically loaded tools are not included in the built-in gated-tool list; their
require_approval-derived default applies. - A changed server tool list is not reflected until its catalog is refreshed with Test.
Use Plugins to understand the built-in integration catalog, Skills when you need reusable instructions for existing tools, and Apps when the workflow needs a dedicated interface.