# Connect Claude.ai connectors to SAM.gov data

To connect Claude.ai to SAM.gov data, add a custom connector with the server URL https://samgovapi.io/api/mcp and a request header Authorization: Bearer <your key>. On Pro and Max this is under Customize, Connectors; on Team and Enterprise an owner adds it in organization settings and members click Connect.

A custom connector puts the samgovapi tools in every Claude.ai chat, on the web and in the apps. Because connectors authenticate with a fixed request header, the key belongs to whoever configures the connector; on Team and Enterprise that means every member shares the organization's key and its credits.

- Connects with: MCP
- MCP server: https://samgovapi.io/api/mcp
- REST base: https://samgovapi.io/api/v1
- Auth: Authorization: Bearer <key>, kept in SAMGOVAPI_API_KEY

## Get a key

Free key at https://samgovapi.io/sign-up, or have the agent call start_signup and approve the link it shows you. Claude.ai stores request header values encrypted. Use a key created for the connector so you can revoke it alone.

## Set up Claude.ai connectors

1. Individual plans: Customize, Connectors, Add, Add custom connector. Enter the URL and add a request header Authorization with the value Bearer followed by your key.

Connector fields:

```
Name: samgovapi
Remote MCP server URL: https://samgovapi.io/api/mcp
Request header: Authorization
Value: Bearer sg_...
```

2. Team and Enterprise: An owner opens Organization settings, Connectors, Add, Custom, Web, enters the URL and the header. Members then find samgovapi in their connectors and click Connect.

3. Use it in a chat: Open the + menu, Connectors, and switch samgovapi on for the conversation.

## Finish account setup once

Data tools unlock after the account answers its onboarding questions: ask the agent to set up your samgovapi account (get_onboarding_questions, then answer_onboarding). Free.

## Check that it works

Ask: "Is UEI ZXBCU6K5KL99 registered in SAM.gov, and when does its registration expire?"

Expected tool call:

```json
{"name":"registration_status","arguments":{"id":"ZXBCU6K5KL99","user_request":"check a registration and its expiry"}}
```

## Things to know

- Free accounts can add one custom connector.
- With no header, the keyless tools still work: search and fetch over the public lookup pages, plus signup and feedback.

## Troubleshooting

- Only search and fetch work: The connector has no Authorization header, so only keyless tools run. Edit the connector and add it.
- Team members cannot see the connector: An owner has to add it at organization level before members can connect.
- ONBOARDING_REQUIRED: Ask Claude to answer the samgovapi onboarding questions for the account.

## Questions

### Does the whole team share one key?

Yes, on Team and Enterprise the connector's header is the organization's. Credits come from that account.

## Official documentation

- Claude Help: custom connectors with remote MCP: https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp

Checked 2026-11-13. All guides: https://samgovapi.io/agents.md

Independent. Not affiliated with, endorsed by or sponsored by GSA, SAM.gov or any U.S. government agency. Registering in SAM.gov is free at sam.gov.