Skip to content
Custom Connectors

Connect Internal referral portal to Claude Code

Let Claude file referrals and move them through review in your internal referral portal. From the terminal, inside the sessions where you already work.

How do you connect Internal referral portal to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Internal referral portal, you add a Internal referral portal MCP server: a small hosted service that exposes Internal referral portal's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Internal referral portal account. No API keys pasted into config files.

claude mcp add --transport http internal-referral-portal https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Internal referral portal once connected?

Full read-write referral portal access lets Claude submit a new referral with the right contact and context, attach supporting notes, advance an entry's status, assign a reviewer, and record an outcome once you approve. The intake and follow-through that used to mean manual form-filling happen inside the portal itself.

  • Submit a new referral with candidate or contact details and context
  • Attach notes, source, or supporting links to an existing referral
  • Update a referral's status as it moves through review stages
  • Assign or reassign a reviewer or owner to a referral
  • Record an outcome or disposition once a referral closes
  • Find referrals matching a query and propose batched status updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Internal referral portal access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Internal referral portal API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Internal referral portal changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Internal referral portal connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Internal referral portal connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Internal referral portal account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Internal referral portal's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Internal referral portal?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Internal referral portal account it signs in with. Revoking access is one click in Internal referral portal.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.