Orsa,
inside Claude.
The Orsa MCP server turns every one of our endpoints into a tool your Claude Desktop (or any MCP-compatible client) can call directly. Ask Claude to chart a website, extract a brand kit, or decode a transaction — and it happens in the chat.
Integration flow
Host
inside Claude
Auth
ORSA_API_KEY
Tools
3 ready workflows
Start free, no card required, most teams ship a first integration in under ten minutes.
The integration should feel
like a product surface
These pages now explain the workflow the integration enables, not just the installation command.
Tool calls for scrape, brand, classify, and crawl endpoints
Shared auth via `ORSA_API_KEY` on the MCP process
Works with any MCP-compatible host — not only Claude
From install command
to production workflow
The page now teaches how the integration fits into the customer's stack before asking them to copy setup code.
Claude Desktop config
Install the integration and attach one Orsa API key.
Use extraction tools
Tool calls for scrape, brand, classify, and crawl endpoints Shared auth via `ORSA_API_KEY` on the MCP process Works with any MCP-compatible host — not only Claude
Brand colors in one prompt
“Chart stripe.com and list primary brand colors.” → maps to `brand.retrieve` / color extraction tools.
- Setup format
- jsonCopy-ready setup block included below.
- Auth
- ORSA_API_KEYSame key for every endpoint and integration.
- Workflow count
- 3Brand colors in one prompt, Markdown capture, NAICS lookup
- Docs
- API referenceUse docs once the integration is connected.
Claude Desktop config
Keep setup concrete and copy-ready, then show the higher-value workflows the integration makes possible.
{
"mcpServers": {
"orsa": {
"command": "npx",
"args": ["@orsa/mcp"],
"env": { "ORSA_API_KEY": "your_key_here" }
}
}
}One key,
many surfaces
Integrations should not feel like wrappers around JSON. They should show how Orsa becomes a reusable context layer inside the tools teams already use.
- Use Orsa from automation tools, AI clients, no-code builders, or your own product.
- Reuse the same endpoint contracts across integrations and custom code.
- Move from a single connected workflow to a broader context platform without changing vendors.
Workflow 01
Brand colors in one prompt
“Chart stripe.com and list primary brand colors.” → maps to `brand.retrieve` / color extraction tools.
Workflow 02
Markdown capture
“Convert this Notion post to Markdown for my doc.” → `web.scrapeMarkdown`.
Workflow 03
NAICS lookup
“What NAICS code fits Blue Bottle Coffee?” → `brand.classify` style tools.
What teams build
once this is connected
Integrations should map to jobs: enrichment, context capture, routing, and automation that makes Orsa part of the customer's existing stack.
Brand colors in one prompt
“Chart stripe.com and list primary brand colors.” → maps to `brand.retrieve` / color extraction tools.
Markdown capture
“Convert this Notion post to Markdown for my doc.” → `web.scrapeMarkdown`.
NAICS lookup
“What NAICS code fits Blue Bottle Coffee?” → `brand.classify` style tools.
Connect Orsa
where your team already works
Start with the integration, then use the same API key for every extraction and brand context workflow.
One API key for every Orsa endpoint · No card required to start.