Connect to Claude.ai

Overview

The Compliancely MCP server exposes your compliance verification tools as native capabilities within Claude.ai. Once connected, you can run checks using plain English — no API knowledge required.

Prerequisites

A Claude.ai account

Pro, Team, or Enterprise plan with MCP access. Sign up at claude.ai

An active Compliancely account

With the verification services you intend to use enabled on your plan.

No API keys needed

Authentication is handled via OAuth 2.1 — you'll log in through a browser prompt during setup.

Setup instructions

Choose your setup method below. The Claude.ai web interface is the quickest option. Cursor and VS Code are available if you prefer working inside your IDE.

Open Claude.ai settings
Go to claude.ai, click your profile icon in the bottom-left corner, and choose Settings.
Navigate to Integrations
In the Settings sidebar, select Integrations (or Connected Apps or Connectors). This section lists all available MCP servers.
Add a new integration
Click Add Integration or Connect an app. When prompted for a server URL, enter:
https://mcp.compliancely.com/mcp
Authorize with Compliancely
Claude will open a Compliancely OAuth consent screen in your browser. Log in with your Compliancely credentials and approve the requested permissions.
Verify the connection
Return to Claude.ai and start a new conversation. Type Check my Compliancely connection — Claude should confirm that the MCP tools are available and list the connected services.

Using tools in Claude

After connecting, just describe what you need in natural language. Here are example prompts for common tasks:

TIN matching

Run a TIN match for Acme Corp with TIN 12-3456789

OFAC sanctions screening

Check if John Smith, DOB 1975-06-15, appears on the OFAC watchlist

Address verification

Verify this address: 350 Fifth Avenue, New York, NY 10118

📘
Tip:
When Claude asks for confirmation before running a tool, review the parameters carefully before approving. This prevents accidental usage charges. Enable tool approval under your Claude settings.

Troubleshooting

Common issues and how to resolve them.

Claude says 'no tools available' or can't find Compliancely

The MCP server may not be connected or the connection was interrupted. Try these steps:

Go to Settings → Integrations in Claude.ai and check that Compliancely shows a green "Connected" status.
If it shows an error, click Disconnect and re-add the server URL https://mcp.compliancely.com/mcp.
Start a fresh conversation — MCP tools are session-bound and may not appear in older chats.

OAuth login fails or authorization screen doesn't appear

Pop-up blockers or browser extensions can prevent the OAuth consent window from opening.

Temporarily disable pop-up blockers for claude.ai and mcp.compliancely.com.
Try the connection in an incognito/private browser window without extensions.
Ensure you have an active Compliancely account with the services you're trying to access enabled.

Tool call returns a 401 or 'Unauthorized' error

Your OAuth token may have expired or been revoked.

In Claude.ai Settings → Integrations, disconnect Compliancely and reconnect. This triggers a fresh OAuth flow and issues a new token.
Check that your Compliancely account is active and not suspended at compliancely.com.

Tool returns a 402 'credit_message' error

Your Compliancely account has run out of credits for the requested service.

Log in to your Compliancely account and navigate to Billing to top up credits or upgrade your plan. Credits are consumed per POST/verification request.

Claude runs the tool multiple times for a single prompt

This is expected AI behavior when Claude infers that a task requires multiple calls (e.g. checking a list of TINs). To prevent this:

Enable tool approval in Claude settings so you can review and approve each call individually.
Be explicit in your prompts: "Run a single TIN match for..." rather than an open-ended instruction.

Tools appear in Cursor/VS Code but return connection errors

IDE-based MCP connections require HTTPS. Verify that your network or corporate firewall allows outbound HTTPS traffic to mcp.compliancely.com on port 443.

If you're on a corporate network, contact your IT team to whitelist mcp.compliancely.com.

Security & best practices

Enable tool approval

Always require human review before Claude executes any Compliancely tool call. Prevents unexpected credit usage.

Limit OAuth scopes

Only approve the permissions relevant to your workflows during the OAuth consent screen.

Avoid chaining MCP servers

Using multiple MCP servers simultaneously can expose you to prompt injection risks from untrusted sources.

Revoke access when done

Manage connected applications in your Compliancely account settings. Revoke Claude access if no longer needed.

Support

Need help? Reach the Compliancely team through these channels.

[email protected]