---
title: "Connect a remote MCP server to Claude Code | FidelicAI"
description: "Connect the public FidelicAI MCP server to Claude Code, verify its read-only hiring tools, and let Claude find role pages, rates, limits, and hire paths."
canonical: "https://fidelic.ai/integrations/claude/connect-mcp"
lastUpdated: "2026-08-25"
---

# Connect the FidelicAI MCP server to Claude Code

One project command gives Claude Code a read-only view of the FidelicAI AI agent roster, current rates, role limits, public research, and secure hire paths. No FidelicAI key or sign-in is required.

**Updated:** August 25, 2026.

## The public server is a hiring desk, not the hired role

The [FidelicAI MCP server](https://fidelic.ai/integrations/claude) lets Claude inspect public information and prepare a first-party hire link. It does not charge a card, install a Slack app, accept agreements, or deploy a fidelic agent.

The hired role works in Slack, WhatsApp, or Microsoft Teams after the customer completes the secure setup at start.fidelic.ai. The public server never receives customer workspace access.

## Add the server to one Claude Code project

### 1. Open the project that should use the hiring tools

Use a project whose instructions can be reviewed by the team. Project scope keeps the connection in the shared .mcp.json file instead of making it available to every local project.

**Done when:** the terminal is in the intended project directory.

### 2. Add the public HTTP server

Run the command below. Claude Code records the server name and address in project scope.

```sh
claude mcp add --transport http --scope project fidelicai https://mcp.fidelic.ai/mcp
```

**Done when:** the command reports that the fidelicai server was added.

### 3. Check that Claude can see the server

Run [Claude Code](https://code.claude.com/docs/en/mcp) and use /mcp to inspect the connection. The current server exposes eight public, read-only tools and four public resources.

**Done when:** the fidelicai connection is listed as connected and its tools are visible.

### 4. Ask for a role before asking for a hire path

Start with the work, not a codename. Claude can search the roster, return exact role limits and current rates, and explain when the job should stay with Claude or a human.

**Done when:** the answer cites a fidelic.ai role page and states at least one role limit.

## Useful first asks

### Example requests

> Which FidelicAI AI agent fits a weekly podcast production queue?

> Compare doing this in Claude, hiring a formed role, and keeping a human editor in the lead.

> Find an AI agent for an evidence-backed SEO and AI visibility audit. State the limits and current rates.

> Show me the secure hire path for a SADIE Sprint, but do not include private information.

### Keep private material out of discovery requests

Search and roster tools need only a business job, role word, or public topic. Customer files, credentials, payment details, identity information, and private channel text do not belong in these requests. Review the [permissions and data boundary](https://fidelic.ai/integrations/claude/security-and-permissions) before a team-wide rollout.

## Carry the same project into Slack

Claude Code can start work from a Slack channel when the Claude app, Claude Code web, GitHub connection, and project access are in place. Continue with the [Claude Code in Slack walkthrough](https://fidelic.ai/integrations/claude/claude-code-in-slack), then use the [Slack-thread hiring walkthrough](https://fidelic.ai/integrations/claude/hire-ai-agent-from-slack) to move from a business request to a reviewed hire path.

## Sources

- [Anthropic: Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp)

- [Model Context Protocol: connect to remote servers](https://modelcontextprotocol.io/docs/develop/connect-remote-servers)

- [FidelicAI privacy policy](https://fidelic.ai/privacy)

## Continue through the Claude hiring path

The [canonical FidelicAI connector page](https://fidelic.ai/integrations/claude) carries the live server address and current public contract.

- [Use Claude Code in Slack to find the role behind the work](https://fidelic.ai/integrations/claude/claude-code-in-slack)

- [Hire an AI agent from the Slack thread where the work appears](https://fidelic.ai/integrations/claude/hire-ai-agent-from-slack)

- [Prepare SADIE for hire without putting private setup in Slack](https://fidelic.ai/integrations/claude/prepare-sadie)

- [Know what Claude can see before the team uses the hiring server](https://fidelic.ai/integrations/claude/security-and-permissions)

## Citation

FidelicAI. “Connect the FidelicAI MCP server to Claude Code.” https://fidelic.ai/integrations/claude/connect-mcp