Edda MCP
The MCP allows users to query Edda in plain English (‘natural language queries’) from any connected AI platform, and get structured answers instantly without logging into Edda, building a report, or exporting data manually.
What is an MCP and what are its capabilities?
MCP (Model Context Protocol) is an open-source standard for connecting AI applications to external systems.
Using MCP, AI applications like Claude can connect to data sources (e.g. local files, databases), tools (e.g. search engines, calculators) and workflows (e.g. specialized prompts, enabling them to access key information and perform tasks on behalf of the user.
When you connect Edda MCP server to an AI tool like Claude, you expose Edda data to AI platforms
Read Actions Restrictions
Access to data through the MCP respects the same role and permission settings configured in Edda. Users will only be able to query data they are authorised to access.
Read actions 📖
All read actions are permitted across Dealflow, Portfolio, and Contacts. AI can query, filter, summarise, and present Edda data in any format like tables, charts, paragraphs, or exportable documents. The more precise the prompt, the more accurate data you get out of it.
| Module | What AI can read | Example query |
|---|---|---|
| Dealflow | Companies, stages, pipelines, fields, owners, sources, tags and more | "List all companies rejected in the last 6 months in Pipeline X" / "Which companies in the New stage have no owner assigned?" |
| Portfolio | Fund companies, valuations, investment operations, metrics, share classes, and more | "What is the total amount divested across all companies in a specific fund?" / "Show me all open investments with their current valuation and % acquired" |
| Contacts | Contact details, linked companies, job titles, emails, relationship strength, and more | "List all contacts tagged as |
Note: In some cases, rephrasing your query may improve results. For example, "notes added last month" may work better than "notes posted last month." If a query returns unexpected results, try adjusting the wording or ask again.
Users who can configure: Administrators. On an organization account, only an admin can add the connector (Claude) or set up the agent (Copilot). On a personal Claude account, any user can add it themselves.
Connecting Edda to Claude :
For Claude Owner :
If your Claude account is part of an organization, only an administrator can add the Edda connector for the whole team. Once it's added, every member of the organization can connect their own Edda account to it (see the next section).
1. Log in to your Edda account.
2. In the web version of Claude (this currently can't be done from the desktop or mobile app), go to Organization Settings and click Connectors.
3. Click “Add,” then choose “Custom” and select “Web” from the dropdown.
4. Give the connector a name (for example, “Edda MCP”) and paste in the Edda MCP URL : https://eu-dealflow.edda.co/api/v2/mcp
5. Click “Add” in the bottom-right corner.
6. Click “Connect.”
For Non-Owner Users (Organization Accounts) :
Once your administrator has added the Edda connector, it will appear on your account automatically. Make sure you're logged in to your Edda account before connecting.
1. Log in to your Edda account.
2. In Claude, go to Settings and click Connectors.
3. Find the Edda connector and click “Connect.”
4. On the pop-up window, click “Agree and allow access.”
5. Once connected, a checkmark will appear next to Edda. Click on the connection and change the tool permission from “Needs approval” to “Always allow,” so Claude doesn't ask for confirmation every time it uses Edda.
Note: If the connector doesn't appear right away in the Claude app, fully quit and reopen the app. It can take a moment to sync after an admin adds it.
Note: If you have access to multiple Edda workspaces, Claude will default to one automatically. Mention the workspace by name in your prompt if you need a specific one.
For Personal Claude Accounts :
1. Log in to your Edda account.
2. In Claude, go to Settings and click Connectors.
3. Click “Add,” then “Add custom connector.” This option is currently only available in the web version of Claude. If you're using the desktop or mobile app, complete this step at claude.ai in your browser first.
4. Give the connector a name (for example, “Edda MCP”).
5. Paste in the Edda MCP URL : https://eu-dealflow.edda.co/api/v2/mcp
6. Click “Add,” then click “Connect.”
7. Check Settings and Connectors. Edda should now show as “Connected” with a checkmark. Click on the connection and change the tool permission from “Needs approval” to “Always allow.”
8. Test the connection by asking Claude something like: “List my available pipelines in my workspace.”
Connecting Edda to Microsoft Copilot :
Setting up Edda in Copilot is more involved than in Claude. It must be done by an Administrator through Copilot Studio in a web browser (Copilot Studio is not available as a desktop or mobile app). Once it's set up and shared, each team member connects individually.
For Copilot Administrators:
Step 1: Create the MCP tool :
1. Log in to your Edda account.
2. Go to Copilot Studio, and in the left navigation bar click “Tools.”
3. Click “+ New tool.”
4. Select “Model Context Protocol (MCP).”
5. In the Server Name field, give the tool a name.
6. Add a description of at least 30 characters. This field is required.
7. In the Server URL field, paste the URL : https://eu-dealflow.edda.co/api/v2/mcp
8. Under Authentication, select “OAuth 2.0” (the last option in the list). “Dynamic discovery” should already be selected. If not, select it.
9. Click “Create.”
Note: The newly created tool won't show up right away. Refresh the page if you don't see it.
Step 2: Create an agent :
1. In the left navigation bar, go to “Agents,” then click “Create blank agent” in the upper right.
2. Give it a name. You don't need to change any other settings.
3. Click “Create,” and allow a few minutes for Copilot Studio to finish provisioning the agent. Wait until the Agent status turns green and reads “Ready” before continuing.
Step 3: Add the MCP tool to the agent :
1. On the same page, scroll to “Tools” and click “Add tool.”
2. Search for MCP in the available filters and select the tool you created in Step 1. This opens the “Add tool” modal.
3. At the bottom of the modal, click “Not connected,” then “Create a new connection.” On the next modal, click “Create” without entering a display name.
4. A new window opens. Click “Agree and allow access.”
5. The window closes and the “Add tool” modal reappears. Click “Add” and wait for it to finish.
Note: The connection's display name defaults to “Credential Manager.” This is expected behavior from Microsoft's connector system, not an error.
Step 4: Test the connection :
1. In the test chat panel on the right, send a message. For example, try “Give me the list of available pipelines inside my workspace.”
2. If you're prompted with “Let's get you connected first,” click “Open connection manager.”
3. On the “Manage your connection” page, click “Connect” next to the “Not connected” status.
4. On the new modal, click “Submit.” The status will change to “Connected.”
5. Go back to the test chat, click “Retry,” and resend your message.
Note: The first connection attempt sometimes fails. If it does, simply retry.
Step 5: Publish the agent :
1. Once the agent returns a correct answer, click “Publish” in the top right.
2. In the pop-up, check “Force newest version” and click “Publish.”
3. Allow a minute or two after publishing before moving on to the next step.
Step 6: Add the Microsoft Teams channel :
1. On the same page in Copilot Studio, click the “Channels” tab.
2. Select “Microsoft Teams + Microsoft 365.” In the modal that opens, click “Add channel” and wait a few seconds. When this is done you can Edit the channel and select "User can add this agent to a team" and "Use this agent for a group and meeting chat". Save again.
3. Under “Agent preview,” click “See agent in Microsoft 365.” This opens your Microsoft account and the new Edda agent automatically - it will open Copilot ai Web page.
Add the agent.
Please wait 5 minutes after adding the agent.
When the Edda agent is added to Copilot, test the connection to confirm it's working correctly.
Note: It's possible that Copilot will return a blank answer on the first couple off attempts. This is expected - follow the steps below to resolve it.
Steps:
- Start a new chat in Copilot.
- In the new chat, type
@edda. Using "@" allows you to add the agent to the chat. - It may still be necessary to refresh the page a couple of times before the agent responds. This is a known behavior on Microsoft's side, not related to Edda.
- Once the refresh takes effect, the agent will return a response, and the "Connection Manager" option will be displayed again.
- Click Connection Manager, then click Connect again.
- After reconnecting, type your prompt as usual - it will now work correctly.
Sharing access with your team :
1. In Copilot Studio, go to “Agents” and select Edda from the list.
2. Open the “Channels” tab and select “Microsoft 365 and Teams.” A sidebar will open.
3. Under “Agent preview,” click “Availability options.”
4. Click “Copy link” for Microsoft Teams.
5. Share this link with everyone on your team who needs access.
Note: Publishing the agent does not automatically grant access to every user in the organization. The link currently needs to be shared manually with each person who needs it.
For Non-Admin Team Members (also adding to Microsoft Teams):
Once your administrator has published the agent and shared the Microsoft Teams link with you, you'll need to connect it to your own account. Every team member needs to complete this individually, whether connecting for the first time or on a new device.
1. Open the Teams link your administrator shared with you. (You can also open it in a browser by clicking “Use the web app instead.”)
2. Click “Add,” then “Open with Copilot.”
3. Ask the agent a question. You'll be prompted to connect.
4. Click “Open connection manager,” then “Connect,” then “Submit.” The status will change to “Connected.”
5. Return to the chat and re-type your question.
Note: This same flow needs to be repeated any time you connect Teams with Copilot for the first time on a new device or session.
Note: After an agent is published and shared, it can take anywhere from a few minutes up to around 24 hours to become fully available across Teams and Copilot. If it isn't working right after setup, wait a while and try again.
If you run into any issues setting up either integration, reach out to your Edda contact or Edda support.