Pharma MCP Server

Pharma vendor-services MCP. Preview. Available after legal, claims, and AEC are live.

Local serverstdio

What is the Pharma MCP server?

Pharma MCP server exists for a simple reason — assistants are far more useful when they can act on Pharma directly instead of describing what you should do. Pharma vendor-services MCP. Preview. Available after legal, claims, and AEC are live.

What you get

Model Context Protocol servers for Scope.bid vendor dispatch across legal, insurance claims, and AEC services.

Setting it up

Installation goes through your MCP client rather than a global install: point it at @scope-bid/scope-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Pharma is connected, these are the calls the assistant has available:

  • scope_dispatch_matter — send a matter to vendors and get live quotes
  • scope_briefing — daily briefing across all open matters

Configuration and credentials

You will need one environment variable: SCOPE_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the pharma mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pharma's toolset — scope_dispatch_matter, scope_briefing — is a fair guide to whether it matches your workflow. It is maintained by bid.scope; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
scope_dispatch_mattersend a matter to vendors and get live quotes
scope_briefingdaily briefing across all open matters

How to install the Pharma MCP server

{
  "mcpServers": {
    "pharma": {
      "command": "npx",
      "args": ["-y", "@scope-bid/scope-mcp"],
      "env": {
        "SCOPE_API_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SCOPE_API_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Pharma to scope dispatch matter.
  • Use Pharma to scope briefing.

Frequently asked questions

It connects Pharma to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (scope_dispatch_matter, scope_briefing) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Pharma directly.