# Connect FedFinder to your AI workspace

> For AI agents: use the [documentation index](https://www.fedfinder.net/connector-docs/llms.txt). This page is also available as [Markdown](https://www.fedfinder.net/connector-docs/connect.md).

Connect once with your FedFinder account, then start with a read-only search. You need an eligible FedFinder subscription and an AI application that supports remote MCP over Streamable HTTP with OAuth. A FedFinder plan does not include a subscription to the AI application.

## 1. Check your FedFinder connection

Sign in at [app.fedfinder.net](https://app.fedfinder.net/login). For Starter, Pro or Intel, open Settings, then Research connector. Research accounts show Connection and usage in their Research workspace.

Check the connection URL and your allowance. If Research reports extra active seats, the account administrator must resolve them: Research includes exactly one active user. See [plans and limits](https://www.fedfinder.net/connector-docs/plans-and-limits).

## 2. Add a custom remote connector

In your AI application's custom app or connector settings, add a remote MCP server named FedFinder with this exact URL:

```text
https://app.fedfinder.net/mcp
```

Select OAuth authentication when offered. Follow the application's current instructions for enabling custom connectors or requesting administrator approval:

- [ChatGPT custom MCP apps](https://help.openai.com/en/articles/12584461-developer-mode-and-full-mcp-connectors-in-chatgpt).
- [Claude custom remote MCP connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

Availability and menu labels depend on the AI application, plan and administrator settings. These instructions configure a custom connection; they do not establish a ChatGPT directory listing. Do not paste a FedFinder password or bearer token into a chat message.

## 3. Review and approve access

The client opens FedFinder sign-in and consent. Verify that the sign-in page is on `app.fedfinder.net`, confirm the account and review the requested permissions. Approve only the permissions you need. Reading opportunities requires `opportunities:read`; account matches and usage require `matches:read`. Saving or changing records requires `captures:write`.

Return to your AI application and enable FedFinder for the conversation if required. A client with OAuth discovery should discover the authorization endpoints automatically. You do not need to create a client secret. See [security and permissions](https://www.fedfinder.net/connector-docs/security).

## 4. Run a safe first check

Ask:

```text
Use FedFinder connection_usage to show my current allowance and remaining calls.
Then search_opportunities for NAICS 541810 with limit 5 and page 1.
Show official source links and deadlines when present. Do not change records.
```

The example NAICS code is advertising, not a recommendation for your business. Replace it with your actual code. A successful usage check proves the connection works; an empty search does not prove there are no opportunities outside FedFinder's coverage.

## 5. Review one source before saving

Use `get_opportunity` with an identifier returned by the search. Compare the returned record with its official notice, amendments and response route. Ask the assistant to identify missing facts. If you want to save it, explicitly approve `save_opportunity` for that identifier. A research save and a Pursuit Board record are different objects.

## Disconnect later

In FedFinder's connection screen, find Connected applications and choose Disconnect for the named client. Also remove it in the AI application. Existing chat content in that application is governed by that provider's retention settings. Disconnection does not erase prior chats.

## Developer connection notes

The server uses stateless Streamable HTTP. Send MCP messages with POST, not a browser GET. GET and DELETE on `/mcp` return 405 because the endpoint has no standalone stream or session. A POST without authorization returns 401 with a `WWW-Authenticate` discovery pointer; that is expected, not a service outage.

Clients with explicit API-key header support can use an eligible, scoped FedFinder API key instead of OAuth. That is a separate API access policy, not a requirement for Research or the OAuth setup above. See the [public REST API schema](https://app.fedfinder.net/v1/openapi.json). Do not use a generic web-fetch MCP server as a FedFinder transport adapter.

Last reviewed: October 24, 2026.