MCP Integration
Connect Ricca to Claude, Cursor, Windsurf, and any AI app that supports MCP. Query your tags, documents, and assets in plain English. No coding required.
Three steps from question to answer.
Any AI assistant you already use. Claude Desktop, ChatGPT, Gemini, Cursor - no coding required for most of them.
Add the MCP server URL to your AI assistant's settings. Works universally across any MCP-supported tool - no coding required.
Your AI now has live access to your instrument tags, document register, and asset data. Plain English in, real answers out.
Once Ricca is connected, your AI assistant can answer questions about your project data in plain English. No forms, no filters, no spreadsheets.
“How many pressure transmitters are in area 100, and are they all ISA 5.1 compliant?”
Area 100 has 12 pressure transmitters. 10 are compliant. 2 need attention: P-102A should be PT-102A, and PRES-103 should be PT-103.
“Which documents in the Condensate Recovery project haven't been reviewed in over 30 days?”
6 documents haven't been reviewed in 30+ days. The oldest is P&ID-CR-001 at 52 days. I can draft a transmittal for these if you need it.
“Show me all assets in the register that are missing a manufacturer entry.”
17 assets are missing manufacturer info. Most are Rotating Equipment (9 items). Here's the full list sorted by priority.
This is a real conversation in Claude Desktop. Ricca processes the request behind the scenes. The engineer just typed a question.
Find all pressure transmitters in area 100 and check if any violate ISA 5.1 naming conventions.
Ricca: searching tags in area 100, type PT, validating ISA 5.1…
I found 8 pressure transmitters in area 100. Two tags violate ISA 5.1:
P-102A → should be PT-102A (missing type designator)PRES-200 → should be PT-200 (non-standard abbreviation)Find all process equipment in Building 4 missing an equipment qualification status.
Ricca: ricca · list_assets(location="Building 4", filter="missing_qualification")
8 assets in Building 4 have no qualification status recorded. 5 are Reactors, 3 are Heat Exchangers. I can export this list or flag them in your asset register.
Generate your API key, paste the config into your AI tool, and you're done. Your agents get secure, governed access to project data.
Claude.ai users connect with one click via OAuth - no key needed. For Claude Desktop, Cursor, or any other tool, generate an API key from Ricca Settings → API Keys.
OAuth users: find Ricca in the Claude.ai Connectors directory and approve. API key users: paste the block shown and replace YOUR_API_KEY.
Your AI assistant now has live access to your instrument tags, document register, assets, and more. Ask in plain English.
{
"mcpServers": {
"ricca": {
"url": "https://mcp.usericca.xyz/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}33 built-in tools your AI assistant can use the moment Ricca is connected.
Find tags by type, service, area, or P&ID reference across your entire project.
Pull up the full document register for any workspace: numbers, revisions, and status.
Filter your instrument index by loop, tag type, area, or any other field.
Check any tag or equipment ID against ISA 5.1, IEC standards, or your custom project convention. Get specific fix suggestions instantly.
Retrieve equipment records with specifications, manufacturer, and location.
Ask Ricca to extract structured data from any uploaded document.
Book a demo and we'll walk you through connecting Ricca to your AI tool of choice. Takes under five minutes.