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.
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. If you filter egress, allow outbound HTTPS to mcp.alpha-sense.com.
| Client | Credentials |
|---|---|
| Claude | None |
| Codex | None |
| 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 |
Claude
You need Claude Team or Enterprise, with an Owner or admin role.
As an Owner, once:
- Open Organization settings → Connectors.
- Select Add, then Custom. If Claude asks for the connector type, choose Web.
- Enter the URL https://mcp.alpha-sense.com/mcp and name it AlphaSense if prompted.
- Click Add.
Then each user, once:
- Open Customize → Connectors.
- Find AlphaSense, labelled Custom .
- Click Connect and sign in to AlphaSense.
The per-user step can't be done centrally. Include it when you announce the connector — users who skip it report the connector as missing — and send them the overview.
To verify, connect yourself, start a new conversation, and ask:
- What are experts from AlphaSense saying about semiconductor inventory levels?
A working connector returns citations, a Sources list, and a link to open the conversation on AlphaSense.
For the current Claude dialogs, see Anthropic's remote MCP connector guide.
Codex
Each user adds the server and signs in:
| codex mcp add alphasense --url https://mcp.alphasense.com/mcp codex mcp login alphasense |
The Codex CLI, IDE extension, and desktop app share this configuration. See OpenAI's Codex MCP guide.
Microsoft 365 Copilot
Before you begin
You'll need:
- A Microsoft 365 Copilot license for each person who will use the connector.
- The Global Administrator or AI Administrator role in the Microsoft 365 admin center. Other admin roles can't create federated connectors.
- Access to the Teams Developer Portal.
- An active AlphaSense account. Each user signs in with their own AlphaSense credentials, so their entitlements carry through.
- The AlphaSense OAuth credentials, provided by your AlphaSense team.
Configuration values
| Field | Value |
|---|---|
| Name | AlphaSense |
| Description | AI-powered market intelligence designed to help analysts monitor, and synthesize vast amounts of public and private |
| MCP server endpoint | https://mcp.alpha-sense.com/mcp |
| Restrict usage by org | My organization only |
| Restrict usage by app | Any Teams app |
| Authentication type | OAuth 2.0 |
| Client ID | Provided by your AlphaSense team |
| Client Secret | Provided by your AlphaSense 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/tok |
| Refresh endpoint | N/A |
| Scope | N/A |
| Enable PKCE | On |
| Developer name | AlphaSense |
| Website URL | https://alpha-sense.com |
| Privacy policy URL | https://www.alpha-sense.com/privacy-notice/ |
| Terms of use URL | https://www.alpha-sense.com/3p-terms/ |
| Redirect URL |
https://teams.microsoft.com/api/platform/v1.0/o (set by Microsoft, nothing to enter) |
REDIRECT URL: Microsoft uses the same redirect URL for every connector. If sign-in fails or loops, confirm with your AlphaSense team that this URL is allow-listed for your client.
Step 1: Register the OAuth client
This step happens in the Teams Developer Portal and gives you an OAuth client registration ID for Step 2.
- Go to dev.teams.microsoft.com/tools/oauth-configuration.
- Choose New OAuth client registration (or Register client if this is your first one).
- For Registration name, enter AlphaSense. For Base URL, enter the MCP server endpoint from the table above.
- Under Restrict usage, set Restrict usage by org and Restrict usage by app as shown in the table above.
- Enter the Client ID, Client Secret, Authorization endpoint, and Token endpoint from the table above. Leave Refresh endpoint and Scope blank.
- Leave Enable PKCE turned on.
- Choose Save.
- Copy the OAuth client registration ID from the confirmation page. You'll need it in Step 2.
RESTRICT USAGE: Make sure Any Teams app is selected. If you pick a specific Teams app, the connector will save, but every AlphaSense tool call will return a 404.
Step 2: Create the connector
This step happens in the Microsoft 365 admin center. Sign in with your Global Administrator or AI Administrator account.
- Go to admin.cloud.microsoft/#/copilot/connectors/add, or choose Copilot → Connectors → Gallery.
- Under Created by your org, find Create a new connector and choose Add.
- On the Custom connector page, under Connect to MCP server, choose Add.
- Enter the Name (as the display name), Description, and MCP server endpoint from the table above. Use exactly the same endpoint you entered as the Base URL in Step 1.
- Enter the Developer name, Website URL, Privacy policy URL, and Terms of use URL from the table above.
- Set Authentication type to OAuth 2.0 and paste the OAuth client registration ID from Step 1.
- Choose Authorize. When the AlphaSense sign-in window appears, log in with your AlphaSense credentials and approve access.
- Choose Save. AlphaSense appears under Your connections.
Step 3: Review and share
Saving the connector doesn't make it visible to users yet. Your tenant settings and rollout both need to include them. Only the staged rollout (item 4) is optional.
- Go to Agents → Settings → Agent and plugin access and confirm Allow agents and plugins built by your organization is turned on.
- Go to Agents → Settings → User access and confirm the users who should have access are included.
- In Copilot → Connectors → Your connections, select AlphaSense.
- Optional: choose Staged rollout, select Users or Groups, and add a small test group.
- Choose Deploy to all users — after testing in Step 4 passes, if you staged the rollout. Each user will be prompted to sign in to AlphaSense the first time they connect.
Step 4: Test it
- Wait up to 10 minutes for changes to propagate.
- As a test user (not an admin), open Copilot Chat and go to Settings → Sources.
- Find AlphaSense, choose Connect, and sign in with your AlphaSense credentials.
- Start a new chat and try:
Using AlphaSense, summarize Apple's latest earnings.
You should see Copilot call an AlphaSense tool and return an answer with source citations.
Troubleshooting Microsoft 365 Copilot
| Symptom | Likely cause | Fix |
|---|---|---|
| Sign-in fails or loops | Redirect URL not allow-listed | Ask your AlphaSense team to confirm the Microsoft redirect URL is allow-listed for your client |
| Connector saves, but every tool call returns 404 | Registration restricted to a specific Teams app | Edit the Step 1 registration and set Restrict usage by app to Any Teams app |
| Sign-in works, but token exchange fails | Base URL doesn't match the MCP server endpoint | Make the Step 1 Base URL and the Step 2 MCP server endpoint match exactly |
| Only the admin can see the connector | Staged rollout or User access only covers the admin | Add users to the staged rollout and User access, then have them connect in Settings → Sources |
| Users can't find the connector at all | A tenant setting is blocking it | Check, in order: Agent and plugin access, Agents → Tools (not blocked), User access, staged rollout, Copilot license |
| Changes don't show up | Propagation delay | Wait 10 minutes, refresh the admin center, and start a new Copilot chat |
| Tool won't authorize after entering the reference ID | OAuth configuration error | Ask your AlphaSense team to confirm the client ID and secret, and re-enter them in the OAuth configuration (see Step 1) |
To update the client secret, edit the registration in the Teams Developer Portal. That's also the only place you can delete a registration.
Microsoft may update this setup flow over time. For the latest steps, see Microsoft's custom federated connectors documentation.
Other clients
Snowflake and Amazon Quick add AlphaSense as a custom connector with OAuth credentials.
- Ask your AlphaSense account team for a client ID and client secret. Give them the redirect (callback) URL your client uses so it can be allowed.
- Add a custom MCP connector in your client, using the server URL above and OAuth with those credentials. Follow your client's guide:
- Snowflake: MCP connectors
- Amazon Quick: MCP integration
- Have each user connect and sign 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. For AlphaSense's security, privacy, and compliance information, see the AlphaSense Trust Center.
Troubleshooting
Users don't see AlphaSense, or get no AlphaSense results. Have the user connect and sign in — not completing that step is the most common cause. Then check the connector is switched on for the conversation. If it isn't listed at all, confirm it was added for the organization, not only to your personal connectors.
Auth failures. Check the client ID and secret where your client needs them, and confirm the user can sign in to AlphaSense directly.
Entitlement errors or empty results. These come from AlphaSense, not the client. Confirm mcp.alpha-sense.com is reachable from the user's network, then check the user's coverage with your account team.
For setup issues, contact support@alpha-sense.com and say whether the problem affects all users or only some. Include conversation IDs if you have them.