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 .
The public server is a hiring desk, not the hired role
The FidelicAI MCP server 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
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.
Add the public HTTP server
Run the command below. Claude Code records the server name and address in project scope.
claude mcp add --transport http --scope project fidelicai https://mcp.fidelic.ai/mcpDone when: the command reports that the fidelicai server was added.
Check that Claude can see the server
Run Claude Code 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.
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
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.
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, then use the Slack-thread hiring walkthrough to move from a business request to a reviewed hire path.
Sources
Continue through the Claude hiring path
Each guide answers a separate part of the same decision. The canonical FidelicAI connector page carries the live server address and current public contract.
Use Claude Code in Slack to find the role behind the work
Set up Claude Code in Slack, connect the FidelicAI MCP server, and move from a channel request to a reviewed AI agent role, rate, limit, and secure hire path.
Hire an AI agent from the Slack thread where the work appears
Turn a Slack request into a FidelicAI role match, compare the engagement options, prepare a secure hire link, and keep payment and approval outside chat.
Prepare SADIE for hire without putting private setup in Slack
Use Claude in Slack to check SADIE’s podcast-production fit, choose a Day Pass, Sprint, or Retainer, and prepare a short-lived setup handoff for review.
Know what Claude can see before the team uses the hiring server
See what the FidelicAI MCP server can read, which fields its tools accept, how SADIE setup links expire, and which hiring steps always stay outside Claude.