Turn the dashboard into something an agent can finish.
If the only surface is a UI, the agent guesses. If the only MCP is one tool per route, the host moves on. Index the operations. Publish search, get, and call. Then Contract the run.
The dashboard, callable
Build + Contract- 01
Spec
InOpenAPI, GraphQL, or a pasted contract.
- 02
Three tools
OutWe index the ops. Not one tool per route.
- 03
Contract
TabPublished catalog vs the run.
A 386-route dump is not a product an agent can finish.
Start. Tools. Watch.
Simple words. Same MCP.
Start
Your API. One URL.
SpecWAIT
OpenAPIPASTE
Spec
OpenAPI or GraphQL.
IndexOPS
Routes12
Index
We list the ops.
apimcp
MCP
A URL hosts can call.
Tools
Three tools. Not one per route.
Search
search invoice
8 records
Search
Find the record.
Get
get inv_204
ok
Get
Open the item.
Call
call refund
done
Call
Do the job.
Watch
Ship. Check. Repeat.
ContractTAB
ListedOK
UsedOK
Contract
Listed vs used.
hosturl
Connection
The URL still opens.
ShipGATE
ok
same check after release
Ship
Same check after you release.
FAQ
Common questions
| Question | Answer |
|---|---|
| Does every product need OpenAPI? | A dashboard convert needs a contract: OpenAPI, GraphQL, or a pasted spec. A website convert reads the public site. |
| Does a large API become one tool per path? | No. We index the operations. The agent gets three tools and searches the catalog. |
| We already host an MCP. | Add that URL. This page is for teams that have an API and no MCP yet. Contract still applies to yours. |
Publish the product agents can call.Then score the catalog.
OpenAPI, GraphQL, or a pasted spec. Three tools. Contract after you ship.
Build from your API