PitchBook
PitchBook's Premium Connector exposes private capital markets data - companies, investors, funds, and deals - to an agent over MCP.
PitchBook appears in the MCP Library as a credential-gated entry. Access is entitlement-gated on the PitchBook side, which makes this integration unusual: the licensing constraint matters more than the configuration.
See Overview for shared prerequisites and secret-handling guidance.
Connection Details
PitchBook publishes a registration_endpoint, so an automated probe reports that DCR is available. It is not available to QuilrAI. The endpoint accepts registrations only from redirect URIs on PitchBook's partner allowlist, and registering any other callback returns:
{"error": "invalid_redirect_uri",
"error_description": "None of the provided redirect URIs are allowed by the server's whitelist"}
PitchBook's partner allowlist covers the AI vendors it names in its connector programme. A QuilrAI callback is rejected. Until PitchBook either allowlists your gateway callback or issues you an OAuth application, install PitchBook with manual OAuth credentials supplied by your PitchBook account team. Do not plan a rollout around DCR.
PitchBook data is licensed per named seat. Behind a shared gateway, an agent authorized by one licensed user can answer questions for colleagues who hold no PitchBook licence. That is a licence-compliance exposure, not a technical fault, and it is the most important thing to settle before rollout.
Use Access Control to restrict the server to the smart group that actually holds PitchBook seats, and confirm the arrangement with your PitchBook account team before going live.
Prerequisites
- A PitchBook licence that includes the Premium Connector. PitchBook offers it on seat-based, unlimited, and trial licences. Confirm with your account representative before you plan a rollout, because the MCP endpoint sits behind this entitlement and it is not included with every seat.
- Single sign-on enabled on your PitchBook account. The Premium Connector authenticates every user through your identity provider. Accounts that sign in with a PitchBook username and password cannot use it.
- MCP service access switched on for your account. PitchBook enables this per customer. It is not on by default.
- A QuilrAI administrator to register the server, restrict access, and set tool scope before rollout.
Get OAuth Credentials From PitchBook
PitchBook does not have a developer console where you create an OAuth application yourself. The AI tools it lists as partners, such as Claude, ChatGPT, Microsoft 365 Copilot, and Perplexity, are pre-registered by PitchBook. For QuilrAI, you ask PitchBook to register the QuilrAI callback for your account. Plan for a support-ticket turnaround rather than a same-day setup.
-
Confirm your entitlement. Ask your PitchBook account representative to confirm the three items above: licence type, SSO, and MCP service access. If you do not know who your representative is, write to support@pitchbook.com.
-
Get the QuilrAI callback URL. In QuilrAI, go to Settings > AI Gateway > MCP Gateway, click Add MCP server, enter the PitchBook transport URL, and copy the callback URL the setup screen displays. It follows this pattern, where the host is your gateway and the last segment is the slug you chose:
https://mcpgateway.quilr.ai/pitchbook/oauth/callback -
Send PitchBook a registration request. Include everything PitchBook needs to register a confidential OAuth client. You can paste the following into the ticket and fill in the two placeholders:
Subject: Register an OAuth client for the PitchBook Premium Connector (MCP)
We use the QuilrAI MCP Gateway to connect our AI agents to the PitchBook
Premium Connector at https://premium.mcp.pitchbook.com/mcp. Dynamic client
registration rejects our callback with invalid_redirect_uri, so please
register the following client for our account, or add the redirect URI to
your registration allowlist.
Account: <your PitchBook account or company name>
Client name: QuilrAI MCP Gateway
Redirect URI: <the callback URL copied from QuilrAI>
Application type: web (confidential client)
Grant types: authorization_code, refresh_token
PKCE: S256
Token endpoint auth method: client_secret_post
Scopes: openid offline_access
Please return the Client ID and Client Secret through a secure channel. -
Receive the outcome. PitchBook answers in one of two ways, and QuilrAI supports both:
-
Store the secret properly. Put the Client Secret in your approved secret manager and in QuilrAI only. Do not keep it in the support ticket, email, or chat once QuilrAI has it.
If your users reach PitchBook from Claude, ChatGPT, Microsoft 365 Copilot, or Perplexity, you can register PitchBook in QuilrAI with Auth mode set to OAuth passthrough instead. The client signs in to PitchBook through your SSO using the partner's own registration, and QuilrAI forwards that token, applies access control, and logs the call. You still need the licence, SSO, and MCP service access above. In this mode the gateway does not store or refresh tokens, and the server is not available through OneMCP.
Add PitchBook To QuilrAI
PitchBook is listed in the MCP Library as a credential-gated entry, so start there rather than registering the URL by hand.
-
In QuilrAI, go to Settings > AI Gateway > MCP Gateway.
-
Open the MCP Library and select PitchBook. Because the entry is credential-gated, QuilrAI asks for OAuth credentials before it installs anything.
-
Confirm that the callback URL QuilrAI displays on this screen is the one PitchBook registered for you. See Get OAuth Credentials From PitchBook.
-
Paste the Client ID and Client Secret that PitchBook issued, then install the MCP.
Do not switch the entry to Dynamic Client Registration unless PitchBook confirmed that it allowlisted your callback. See the allowlist note above.
-
Click Connect, sign in to PitchBook, review the requested permissions, and approve access.
-
Refresh capabilities and record the tool count in your rollout notes.
If The Library Tile Is Not Available
Register the server manually with the same credentials:
- Click Add MCP server and enter the following values:
- Create the MCP connection, then Connect and refresh capabilities as above.
PitchBook advertises a registration_endpoint, so Auto-detect reports that DCR is available. Registration still fails for a QuilrAI callback because of the allowlist described above. Select OAuth credentials and supply the Client ID and Client Secret from your PitchBook account team.
The Callback URL
The QuilrAI callback URL is issued per MCP server, not once per tenant, and it is displayed on that server's own setup screen. It is built from your gateway host and the server's slug, for example https://mcpgateway.quilr.ai/pitchbook/oauth/callback. Copy the value QuilrAI shows you rather than typing it, and do not reuse a callback from another provider page or another server in the same tenant.
If you delete the server and recreate it with a different slug, the callback URL changes and PitchBook's registration no longer matches. Reuse the original slug, or ask PitchBook to update the redirect URI.
Tools
PitchBook does not publish its MCP tool inventory, so this page cannot state it authoritatively. Discover the surface after connecting:
- Open the server and click Show tools.
- Record every tool name and description in your rollout notes.
- Classify each one as read or write before enabling any of them for agents.
Expect the surface to centre on company, investor, fund, and deal lookups. Treat anything that creates a list, a saved search, or an export as a write until you have confirmed otherwise.
Recommended Read-Only Rollout
- In Access Control, restrict the server to a smart group containing only users who hold a PitchBook seat. Do this before enabling any tools, not after.
- In Tool visibility, disable every tool that is not a plain lookup.
- Set a rate limit on the server. PitchBook data pulls are metered on most contracts, and an unattended agent iterating over a target list can consume a quarter's allowance in an afternoon.
- Review the audit log after the first week and compare query volume against your contract terms.
Verify The Connection
Start with a single bounded, read-only lookup:
Use the PitchBook MCP. Look up one company by name and return its profile
summary only. Do not run a screen, do not export, do not save a search, and do
not iterate over a list of companies.
Confirm that:
- the profile returned matches the company you asked for;
- the authorizing account is the licensed seat you intended;
- no saved search, list, or export was created;
- the MCP client reports the expected tools instead of remaining at Loading tools.
Reconnecting
- Users reconnect after revoking the PitchBook grant, after the latest refresh token is lost, or after the gateway connection is deleted.
- If the Premium Connector entitlement lapses, existing tokens stop returning data. The symptom is usually empty or forbidden responses rather than a sign-in prompt.
- If PitchBook issued a manual OAuth application, update the stored Client ID and Client Secret in QuilrAI whenever those credentials are rotated.
Troubleshooting
Security Notes
- Restrict this server by smart group. It is the one control that addresses the licence exposure described above.
- If PitchBook issues a Client Secret, keep it in your approved secret manager. Never place it in an MCP client configuration file, source control, chat, or a support ticket.
- Keep export and list-creation tools disabled unless a named owner has approved them.
- PitchBook content is licensed third-party data. Anything an agent summarizes from it inherits those licence terms, including material pasted into internal documents.