MCP Connector: Setup
The MCP is part of the Enterprise Suite offering. Request access and your account team will be in touch shortly to discuss how to get started.
Request Access
Every client connects to the same server:
https://mcp.alpha-sense.com/mcp
Each user then connects once with their own AlphaSense sign-in (SSO included), so what they can
retrieve follows their own entitlements, except Broker Research. To verify,
connect yourself and ask a question; a working connector answers with citations. If you filter
egress, allow outbound HTTPS to mcp.alpha-sense.com.
| Client | Credentials |
|---|---|
| Claude | CIMD, no manual credentials |
| ChatGPT | CIMD, no manual credentials |
| Codex | CIMD, no manual credentials |
| Microsoft 365 Copilot | Client ID and client secret from your account team |
| Snowflake | Client ID and client secret from your account team |
| Amazon Quick | Client ID and client secret from your account team |
CIMD (Client ID Metadata Document) clients register themselves with AlphaSense, so there is nothing to enter.
Claude
Requires Claude Team or Enterprise.
- An Owner adds a custom connector in Organization settings → Connectors with the server URL above.
- Leave the OAuth client ID and secret under Advanced settings blank. Claude registers itself with CIMD.
- Each user connects it once in Customize → Connectors and signs in to AlphaSense. This can't be done centrally, so include it when you announce the connector.
See Anthropic's remote MCP connector guide.
ChatGPT
Requires ChatGPT Business, Enterprise, or Edu. Set it up on the web.
- An admin or owner opens Plugins, selects + → Add custom MCP server, enters the server URL above with OAuth authentication, and selects Create as a plugin. On Enterprise or Edu, the role needs Create plugins with MCPs (off by default in Workspace settings → Permissions & roles).
- Don't enter your own OAuth client ID or secret. ChatGPT registers itself with CIMD, and manual credentials override it.
- Publish the plugin to the workspace so members can find it.
- Each user installs and connects it, signs in to AlphaSense, and selects it with @ in a chat.
See OpenAI's Connecting custom MCP servers in ChatGPT.
Codex
Each user adds the server and signs in:
codex mcp add alphasense --url https://mcp.alpha-sense.com/mcp
codex mcp login alphasense
See OpenAI's Codex MCP guide.
Microsoft 365 Copilot
Requires the Global Administrator or AI Administrator role and a Copilot license for each user.
- In the Teams Developer Portal, register an OAuth client with the values below and copy the registration ID.
- In the Microsoft 365 admin center, create a custom MCP connector with the same endpoint and that registration ID, then authorize.
- Allow agents built by your organization, then deploy the connector to your users.
- Each user connects it in Copilot Chat under Settings → Sources and signs in.
| Field | Value |
|---|---|
| Base URL / endpoint | https://mcp.alpha-sense.com/mcp (must match exactly in both steps) |
| Restrict usage | My organization only; Any Teams app |
| Client ID and secret | From your account team |
| Authorization endpoint | https://auth.research.alpha-sense.com/authorize?audience=https%3A%2F%2Fmcp.alpha-sense.com%2F |
| Token endpoint | https://auth.research.alpha-sense.com/oauth/token |
| Refresh endpoint/Scope | Leave blank |
| PKCE | On |
| Privacy policy URL | https://www.alpha-sense.com/privacy-notice/ |
| Terms of use URL | https://www.alpha-sense.com/3p-terms/ |
Select Any Teams app. Restricting to a specific app saves fine, but every tool call returns 404.
See Microsoft's custom federated connectors guide.
Other clients
Snowflake and Amazon Quick add AlphaSense as a custom MCP connector with OAuth.
- Ask your account team for a client ID and secret, and give them your client's redirect URL.
- Add the connector with the server URL above, following Snowflake's guide or Amazon Quick's guide.
- Each user connects and signs in to AlphaSense.
Security
Each user signs in with their own AlphaSense account — there is no shared service account — so retrieval follows their entitlements and activity is attributable to them. See the AlphaSense Trust Center.
Troubleshooting
For problems on a user's side (not connected yet, or not connecting), see the overview's Troubleshooting.
- No users see AlphaSense. In Claude, check it was added in Organization settings, not only as a personal connector. In ChatGPT, check the plugin was published to the workspace.
- Sign-in fails or loops. For CIMD clients (Claude, ChatGPT, Codex), remove any OAuth client ID and secret entered by hand. For clients with a client ID and secret, ask your account team to confirm your redirect URL is allowed.
- Empty results or entitlement errors. Confirm
mcp.alpha-sense.comis reachable, then check the user's coverage with your account team.
For anything else, contact support@alpha-sense.com. Say whether all users or only some are affected, and include conversation IDs if you have them.