Skip to main content

VETR API & MCP is LIVE!Check it out!

Skip to main content

MCP Connection Guide

Connect VETR to Claude Desktop, Cursor, Windsurf, or any MCP-compatible client using the VETR MCP server. Claude and ChatGPT connect with a sign-in; other clients use an API key. More help: connecting AI tools over MCP and how credits work.

Connect Claude or ChatGPT with a sign-in

No key to copy. You sign in with your VETR account and approve what the connector may do, for the workspace you are working in. You can disconnect at any time under Settings, API Tokens, Connected apps.

Claude (connector)

The simplest way to use VETR in Claude on the web or in Claude Desktop: add it as a custom connector. You sign in with your VETR account and approve access for the workspace you are working in, so there is no key to copy.

In Claude, open Settings, then Connectors, then add a custom connector, and enter

Name: VETR Proposal
MCP server URL: https://vetrproposal.com/mcp/vetr

Claude opens VETR so you can sign in and approve access. VETR shows which workspace the connection is for (the one you are working in) and what it may do (read, or read and write). You can disconnect at any time under Connected apps, in Settings or in the developer console.

ChatGPT

ChatGPT can connect to VETR as a custom connector (MCP server) with OAuth sign-in, where custom connectors are available on your plan. Two alternatives use a VETR API key instead: a Custom GPT with an Action, or the OpenAI API with a remote MCP tool.

Option 1: Custom connector (OAuth). In ChatGPT, add a custom MCP connector, choose OAuth for authentication, and enter

Name: VETR Proposal
MCP server URL: https://vetrproposal.com/mcp/vetr

Menu names and plan availability change often. If the in-app connector screen offers an API-key or header option in your version, use the server URL and a bearer header from the Other tab.

Using Cursor, Windsurf, a Claude Desktop config file or another client? Follow the API-key steps below.

Before you start

  • A VETR API key — get one free (no credit card, starter credit included).
  • Your MCP client installed and running (Claude Desktop, Cursor, etc.).
  • A text editor to update the client's config file.
1

Get your API key

Sign up at the developer portal. A read-only token named Default API Key is created automatically — no setup wizard. Once signed in, your key appears on the developer dashboard.

Already have a VETR account? API tokens live at Settings → API Tokens. Create a new token with the read ability for MCP.

2

Configure your client

Edit ~/.config/claude/claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "vetr": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://vetrproposal.com/mcp/vetr", "--header", "Authorization: Bearer YOUR_API_KEY"]
    }
  }
}

Replace YOUR_API_KEY with the token from your dashboard. The key is sensitive — do not commit it to a repository.

3

Restart and verify

Restart your AI client after saving the config. The VETR tools should appear in the tool panel. Try a quick test:

“Use the search-proposals-tool tool to list my most recent proposals”

You should see your VETR proposals in the response. If the tool list is empty or you get an authentication error, see troubleshooting below.

The 20 tools

Every tool is listed here, from the same source as the server. A default read-only key or sign-in covers the read tools. The four marked write change data or send it out and need write access. Lookups and FedProc-1 can spend credit on a developer workspace.

search-proposals-toolSearch proposals

Find proposals by title, agency, or status

get-proposal-detail-toolGet proposal detail

Full proposal data including VETR score breakdown

get-compliance-status-toolCompliance status

Requirements met / in-progress / missing with score %

get-vetr-score-toolVETR score

Value, Experience, Teaming, Responsiveness breakdown

search-partners-toolSearch partners

Teaming partners by capability, cert, or name

export-proposal-to-drive-toolExport to Drivewrite

Push a proposal to your GovCloud Google Drive

notify-gov-slack-toolNotify GovSlackwrite

Post a status update to your GovSlack channel

search-opportunities-toolSearch opportunities

Live federal contract opportunities by keyword, NAICS or set-aside

search-grants-toolSearch grants

Live federal grant opportunities by keyword or agency

search-awards-toolSearch awards

Past federal contract awards for competitor and pricing research

search-forecasts-toolSearch forecasts

Agency procurement forecasts for upcoming work

get-credit-balance-toolCredit balance

Your prepaid balance and whether model calls are paused

get-usage-summary-toolUsage summary

This month: calls, model spend and success rate

fedproc-1-generate-toolGenerate with FedProc-1

Writes to the VETR standard with live data lookups. Spends credits.

list-proposal-sections-toolList proposal sections

The outline of a proposal with status and word counts

get-proposal-section-toolRead a proposal section

The text of one section of a proposal

update-proposal-section-toolWrite a proposal sectionwrite

Replace a section’s text and move it through draft, review and final

list-rfps-toolList solicitations

The solicitations in your organization

get-rfp-requirements-toolSolicitation requirements

Extracted instructions, criteria and clauses for a solicitation

create-proposal-toolCreate a proposalwrite

Start a draft proposal against one of your solicitations

Troubleshooting

Tools don’t appear in the client

Make sure you restarted the client after saving the config. Check the config file path — on macOS the Claude Desktop path is inside ~/Library, not ~/.config.

401 Unauthorized

The API key is missing or wrong. Copy it again from your developer dashboard. Check there are no trailing spaces in the Authorization header.

403 Forbidden

Your organization’s plan does not have API access enabled, or your email address is not verified. Check your plan on the developer dashboard.

429 Too Many Requests

You are sending requests too quickly, or the workspace is on a legacy monthly quota. Wait a moment and retry, and check usage in the console. A 402 means the credit balance is empty: add funds in Billing.

The client connects but results are empty

A new developer workspace starts with no proposals. Create a test proposal in VETR first, or use the search-partners-tool tool which searches the shared partner database.

Further reading

Ready to connect?

Sign up for free, verify your email, and create your API key.