Turn a site, API, or command into an https MCP.
Build is the source. The URL feeds the MCP tabs you already have: Connection, Contract, Discoverability, hosts, Live Traffic, Analytics.
Then the same MCP
AgentStatus- 01
Build
SourceWebsite, dashboard API, or command becomes one https URL.
- 02
Connection
TabWe open that URL as AgentStatus. Transport, auth, list, call.
- 03
The rest of the tabs
TabsContract, Discoverability, hosts, Analytics. Same MCP, not a side product.
You do not get a separate convert workspace. The URL lands on the MCP you already know.
Build, then the same tabs.
The convert is not a side workspace. Connection opens the URL. The other tabs keep the record.
What you start from
Pick the source. The output is an https MCP, not a new product.
Website
The public site becomes a catalog. Agents use what is on the site.
Dashboard
OpenAPI, GraphQL, or a pasted spec becomes lookups. Not one tool per route.
Command
A local stdio MCP becomes a hosted link. The tools you wrote stay.
It feeds the MCP you already have
The URL is a normal MCP. Connection, Contract, and Discoverability read it the same way they read any server you add.
Connection
We open the hosted URL as AgentStatus. Reach, auth, negotiate, list, call. One run, one record.
Contract
The published catalog vs the run. What Build listed is what Contract checks the hosts actually used.
Discoverability
Did Claude offer the MCP. Did the answer name you.
Hosts, traffic, Analytics
After Connection holds, the other tabs walk the same URL. Build does not skip Host Compatibility or Live Traffic.
How hosts differ
Cursor, Claude Code, Codex, and the rest start that URL. Each sitting keeps the tool that host called.
Live Traffic
Real calls and jobs on that MCP. observe() for the server. Not a convert-only log.
Analytics
The same Analytics tab as any MCP you added. Runs, tool success, host mix. Build is the source, not a second grade.
FAQ
Common questions
| Question | Answer |
|---|---|
| Is Build a separate product from Connection? | No. Build makes the https URL. Connection, Contract, Discoverability, hosts, Live Traffic, and Analytics are the same tabs as an MCP you already host. |
| Does every dashboard need OpenAPI? | A dashboard convert needs a contract: OpenAPI, GraphQL introspection, or a pasted spec. A website convert reads the public site. A command convert keeps the tools you already have. |
| Does a 386-route API become 386 tools? | No. We index the operations. The agent gets three tools and searches the catalog. Contract still scores the catalog that was published. |
| Is this the same as adding an MCP you already host? | Add an MCP is a URL you already run. Build turns a site, API, or command into that URL. After that, the tabs are the same. |
Build makes the URL.The MCP tabs grade what hosts do with it.
Pick Website, Dashboard, or Command. Copy the https link. Connection, Contract, and the rest of the tabs pick it up.
Build an MCP