Developer docs
Robotico MCP Server
Robotico exposes a hosted Model Context Protocol server for agents that need structured humanoid robotics intelligence, source evidence, review workflows, and audit trails from Robotico. Agent operating playbooks are available in the MCP Agent Guide.
Endpoint
- Transport
- Streamable HTTP
- URL
https://robotico.market/mcp- Authentication
- Developer bearer token in the Authorization header.
Remote MCP config
Use this shape in MCP clients that support remote Streamable HTTP servers. Replace the token placeholder with a Robotico developer API token.
{
"mcpServers": {
"robotico": {
"url": "https://robotico.market/mcp",
"headers": {
"Authorization": "Bearer rbt_..."
}
}
}
}Tokens and auth
Tokens are created from developer settings after signing in. The current public access model is developer API token auth, not OAuth. Robotico does not expose an OAuth authorization server for MCP clients at this time. Company and robot write tools require a token owned by the assigned company representative or a Robotico admin account.
What it exposes
- Company directory and profile search across humanoid robotics and embodied AI companies.
- Robot and product lookup with manufacturer relationships, structured specifications, classification, availability, aliases, images, and variants.
- Robot field evidence with source citations, extracted quotes, screenshots, and page snapshots.
- Company and robot write tools for assigned company representatives and Robotico admins, including review-first robot update candidates.
- Entity-scoped audit logs for company, robot, and generic entity mutations.
- Industry statistics, market overview, rankings, funding, and growth data.
- Article search and retrieval for Robotico analysis and market signals.
- Timeline event listing, duplicate detection, entity timelines, event search, sources, and change history.
Example use cases
- Search companies by category (humanoid, enabler, distributor), country, funding stage, ticker, or robotics focus.
- Lookup robots and compare specifications, applications, capabilities, status, commercial availability, variants, and manufacturer context.
- Attach evidence to robot fields such as tagline, status, or specifications.height without changing the profile value.
- Stage risky robot changes for review, including rename, status, classification, category, description rewrite, and variant merge or split proposals.
- Let company representatives update public company details and low-risk robot facts from approved agent workflows.
- Use audit logs to explain what changed after company, robot, or entity write operations.
- Pull industry stats for market maps, rankings, briefing notes, and investor research.
- Find timeline duplicates before event creation, then add sources, link entities, or publish approved candidates.
- List or search articles and timeline events to ground agents in recent Robotico signals.
Discovery metadata
MCP crawlers and directories can read the registry-style server document at https://robotico.market/.well-known/mcp/server.json.