Obsidian Regulatory MCP vs RegAffairs AI
A side-by-side look at the Obsidian Regulatory MCP and RegAffairs AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RegAffairs AILegal · Remote HTTP/SSECited answers on chemical, food, pharma, device, cosmetic and pesticide rules, linked to sources.43FairAuth: no auth requiredVerdict: choose Obsidian Regulatory MCP for legal work over a hosted endpoint; choose RegAffairs AI for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Obsidian Regulatory MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
RChoose RegAffairs AI when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R RegAffairs AI | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 40/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Obsidian Regulatory MCP | View RegAffairs AI |
Tools & capabilities
Obsidian Regulatory MCP tools
No tool names declared yet. Check the project README from the listing page.
RegAffairs AI tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Obsidian Regulatory MCP
{
"mcpServers": {
"obsidian-regulatory-mcp": {
"url": "https://obsidianri.com/mcp"
}
}
}
RegAffairs AI
{
"mcpServers": {
"regaffairs-ai": {
"url": "https://regaffairsai.com/docs/mcp"
}
}
}
Frequently asked questions
Obsidian Regulatory MCP is categorized under Legal and uses a remote HTTP/SSE transport. RegAffairs AI belongs to Legal and uses a remote HTTP/SSE transport. Pick Obsidian Regulatory MCP for legal work and RegAffairs AI for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Obsidian Regulatory MCP has no declared pricing — check the project's own site. RegAffairs AI has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add obsidian-regulatory-mcp and regaffairs-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Obsidian Regulatory MCP has a quality signal of 40/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. RegAffairs AI has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.