MCP spec
The server, its three tools, and how a client connects.
One server gives any MCP client every operation of every Startup its token reaches.
Endpoint
https: //api.sb/ mcpStreamable HTTP. Clients sign in with OAuth; the token carries the caller's namespace and scopes.
Tools
| Tool | Does |
|---|---|
search | Finds records, Nouns, Verbs, and docs by keyword, meaning, or filter. |
fetch | Returns one record, list, or definition by id or path; /$.d.ts returns the types of $. |
do | Runs a short TypeScript program with the typed $ in scope, as one Action. |
Input schemas
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "What to find."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 100,
"default": 10
}
},
"required": [
"query"
]
}The do program
do runs the body of an async function with $ in scope, the same client as the SDK. One run is one Action. Fetch /$.d.ts first for the caller's types.
const offer = await $.Offer.publish({ offer: 'offer_1' })
return offerConnect a client
claude mcp add --transport http startup-builder https: //api.sb/ mcp