MCP Servers
MCP (Model Context Protocol) servers are external services that expose tools, resources and prompts. Connect one to your company and its tools become importable as Autessa tools your agents can call. The whole lifecycle is scriptable — this namespace has no web-app-only commands.
Key concepts
Commands are server-*, not nested
Unlike most namespaces, MCP flattens its verbs into the command name: server-create, server-get, server-list-tools. The one plural is servers-list — note the s moves.
Auth is write-only
authConfig can be set but is never returned. Reads only report whether auth is configured, via hasAuthConfig. If you lose a credential you re-set it; you cannot read it back.
Listing is live
server-list-tools, server-list-resources and server-list-prompts query the server itself at call time rather than returning a cached snapshot. They tell you what the server exposes now, which also makes them a connectivity check with detail.
How to connect a server
autessa mcp server-create \
--name "Internal docs" \
--serverUrl "https://mcp.example.com/sse" \
--description "Company documentation search." \
--authType BEARER \
--authConfig '{"token":"..."}'
authType defaults to NONE; authConfig is required unless it is NONE, and its shape depends on the type — an API key, a bearer token, basic-auth credentials, or custom headers. It is passed as a JSON string.
Verify before you rely on it:
autessa mcp server-test-connection --json '{...}'
Probes the server to check it is reachable and authenticates — the first thing to run when an imported tool starts failing.
How to see what a server offers
autessa mcp servers-list
autessa mcp server-get --json '{...}'
autessa mcp server-list-tools --json '{...}'
autessa mcp server-list-resources --json '{...}'
autessa mcp server-list-prompts --json '{...}'
Read server-list-tools before importing — it is the definitive list of what you are about to pull in.
How to import its tools
Importing happens from the tools namespace, not here:
autessa tools create-from-mcp --json '{...}'
This bulk-creates an Autessa tool for every tool the server advertises. Imported tools are tagged mcp plus the server host, so autessa tools all lets you find them again — and tell them apart from hand-built ones.
From there they behave like any other tool: publish them, attach them to an agent, and their runs land in tools history list like everything else.
How to update and disconnect
autessa mcp server-update --json '{...}'
autessa mcp server-delete --json '{...}'
server-delete disconnects the server's tools, resources and prompts from your company. Tools already imported and attached to agents are affected — check autessa tools all for anything tagged with that server's host before deleting.Full command reference
| Command | What it does |
|---|---|
| autessa mcp server-create | Connect a new MCP server. |
| autessa mcp server-delete | Delete an MCP server config, disconnecting its tools/resources/prompts from your company. |
| autessa mcp server-get | Fetch one MCP server config by id (auth redacted). |
| autessa mcp server-list-prompts | List the prompt templates a connected MCP server exposes (queried live from the server). |
| autessa mcp server-list-resources | List the resources a connected MCP server exposes (queried live from the server). |
| autessa mcp server-list-tools | List the tools a connected MCP server exposes (queried live from the server). |
| autessa mcp server-test-connection | Probe an MCP server to check it is reachable and authenticates. |
| autessa mcp server-update | Update an MCP server config. |
| autessa mcp servers-list | List every MCP server connected in your company (auth redacted). |
Related
- Tools — import and publish MCP tools
- Agents — attach them
- MCP servers in the builder
- MCP tool types
- MCP API