MCP Servers
An MCP Server is a connection, prefixed MCP_, to a remote Model Context
Protocol server whose discovered tools the
Simba agent can call.
This is Perpetual driving something else. For the opposite direction, an outside agent driving Perpetual through Perpetual's own MCP endpoint, see MCP access.
An MCP Server is content.
It points at a remote endpoint over Streamable HTTP, connects with a set of
request headers, and caches the tools the endpoint advertises through the MCP
tools/list call. The agent can call each cached tool under the namespace
mcp_<name>_<toolName>, alongside the Skills and
HTTP Tools it also uses. Connection headers can carry
credential references, so a bearer token or API key stays out
of the stored configuration. Rediscovery reconnects to the endpoint
and refreshes the cached tool list while keeping the per-tool overrides
you have set.
Discovered tool
Each entry in discoveredTools describes one tool the server advertised.
Rediscovery replaces the cached names and schemas from the server. It preserves
the enabled and requiresApprovalOverride values you have set on tools that
still exist.
| Field | Type | Required | Description |
|---|---|---|---|
name | string | Required | The tool name as the server reports it. Perpetual combines it with the server name to form the agent-facing mcp_<name>_<toolName>. |
description | string | Optional | The tool description from the server. |
inputSchema | object | Optional | The tool's input JSON Schema from the server. Perpetual exposes the tool to the agent only when this is a valid object schema. |
readOnlyHint | boolean | Optional | The server's hint that the tool does not modify state. Drives the default approval behavior. |
destructiveHint | boolean | Optional | The server's hint that the tool performs a destructive change. |
enabled | boolean | Required | Whether the tool is available to the agent. Default true. Perpetual does not expose a disabled tool. |
requiresApprovalOverride | boolean | Optional | Overrides whether a call needs human approval. When unset, the default applies. The default gates any tool that is not read-only and lets read-only tools run without approval. |
Inputs
| Field | Type | Required | Description |
|---|---|---|---|
name | string | Required | Server name. Lowercase letters, digits, underscores, and hyphens only. Doubles as the tool namespace, so Perpetual exposes a discovered tool to the agent as mcp_<name>_<toolName>. |
url | string | Required | The remote MCP server endpoint, reached over Streamable HTTP. |
headers | object | Optional | Request headers sent on every connection, as a string-to-string map. Values support Liquid templating and credential.* references, so a header can resolve a stored credential at connection time. |
folderPath | string | Optional | Folder location within the Space, e.g. MCP/PagerDuty. |
Outputs
| Field | Type | Description |
|---|---|---|
discoveredTools | array<object> | The tools the server advertised, cached from its tools/list response. Each entry is a discovered-tool object (above). |
lastDiscoveredAt | timestamp | When Perpetual last refreshed the tool list from the server. Null until the first discovery. |
Plus the common resource fields.
Related
- Skills, reusable agent instructions in the same Space.
- HTTP Tools, single-endpoint agent tools defined in Perpetual.
- Credentials, the stored secrets a connection header can reference.
- Content, the authored resource types the Perplexicon covers.