Skip to content

Commit 2dd6000

Browse files
committed
Scope MCP catalog claims to eligible operations
1 parent 169f977 commit 2dd6000

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

‎content/agents/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Connect your coding agent to Spacefast once, then ask it to publish. This page c
77

88
## What an agent can do
99

10-
Anything you can do in the dashboard, an agent can do over MCP. Every Spacefast API operation is its own MCP tool, named by its operation ID: `getAccount`, `listSpaces`, `searchDocs`, `createDomain`, and a few hundred more. Clients that support tool search load them on demand.
10+
The MCP catalog exposes eligible API operations as individual tools. Each tool uses its operation ID: `getAccount`, `listSpaces`, `searchDocs`, `createDomain`, and a few hundred more. Clients that support tool search load them on demand.
1111

1212
A handful of tools sit on top of that catalog.
1313

‎content/agents/mcp-server.mdx‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ You don't need this page. It's the technical reference for wiring up the MCP ser
1111

1212
## Two runtimes, one tool catalog
1313

14-
The same server ships in two runtimes. Both expose every Spacefast API operation as its own tool. The difference is the filesystem.
14+
The same server ships in two runtimes. Both expose each eligible Spacefast API operation as its own tool. The difference is the filesystem.
1515

1616
| | Hosted | Local |
1717
|---|---|---|
@@ -73,11 +73,11 @@ The local server takes its credential from the process, never from client config
7373

7474
### Operation tools
7575

76-
Every API operation an agent may call is a tool named by its `operationId`: `getAccount`, `listSpaces`, `searchDocs`, `createDomain`, `promoteSpaceVersion`, and a few hundred more. Its input schema is the operation's own contract, with `path`, `query`, and `body` groups. Its result is the API response. There is nothing to discover at runtime and no program to write: read the schema from `tools/list`, then call the tool.
76+
Each API operation exposed through MCP is a tool named by its `operationId`: `getAccount`, `listSpaces`, `searchDocs`, `createDomain`, `promoteSpaceVersion`, and a few hundred more. Its input schema is the operation's own contract, with `path`, `query`, and `body` groups. Its result is the API response. There is nothing to discover at runtime and no program to write: read the schema from `tools/list`, then call the tool.
7777

7878
That is a big list. Clients that support tool search load the tools they need on demand. A client that loads everything up front still works, just with a larger tool list.
7979

80-
A few operations stay in the dashboard, such as buying a domain, and a few stay in the CLI and API, such as claiming an anonymous Space with its key. Those have no tool.
80+
A few operations stay in the dashboard, such as buying a domain. The `domains:write` scope does not add a domain-purchase MCP tool. A few stay in the CLI and API, such as claiming an anonymous Space with its key. Those have no tool.
8181

8282
### Product tools
8383

0 commit comments

Comments
 (0)