MCP lets Codelia connect to external tool servers. Use it when you want the TUI coding agent to access tools that are not built into the local runtime.
Common use cases:
- connecting project-specific tool servers
- talking to remote HTTP MCP endpoints
- exposing local stdio-based tools through MCP
- giving the agent access to external systems in a structured way
The config/CLI transport names are:
httpstdio
More precisely:
httpis the current Streamable HTTP transportstdiois the local process transport
In practice:
- use
httpfor remote/shared servers - use
stdiofor local tool processes
A good first workflow is:
codelia mcp add my-server --transport stdio --command uvx --arg my-mcp
codelia mcp list
codelia mcp test my-serverThen launch the TUI and inspect loaded MCP servers with:
/mcp
Most MCP commands accept scopes.
projectkeeps the server config in the current repoglobalmakes it available more broadlyeffectiveis the merged view used by listing/testing
A practical rule:
- use
projectfor repo-specific servers - use
globalfor personal shared servers
List servers:
codelia mcp list
codelia mcp list --scope effectiveAdd a stdio server:
codelia mcp add local-demo --transport stdio --command uvx --arg my-mcpAdd an HTTP server:
codelia mcp add remote-demo --transport http --url https://example.com/mcp --scope globalTest a server:
codelia mcp test local-demoDisable or remove a server:
codelia mcp disable local-demo
codelia mcp remove local-demoIf an MCP server needs auth, manage its tokens with:
codelia mcp auth list
codelia mcp auth set my-server --access-token <token>
codelia mcp auth clear my-serverFor HTTP servers, codelia mcp test automatically uses a stored bearer token when one exists for that server id.
Inside the TUI, /mcp is the fastest way to inspect currently loaded MCP server state.
Once a server is configured and available, the agent can use the tools exposed by that server during a run.
- CLI reference:
reference/cli.md - Skills:
skills.md - AGENTS.md:
agents-md.md