Sedna's MCP server lets AI assistants such as Claude and Microsoft Copilot work directly with your Sedna workspace. Ask a question in your assistant and it pulls up a contact, gathers everything filed against a voyage, reads an attachment, or searches your team inboxes, then answers in context.
It uses the open Model Context Protocol, so any MCP-compatible assistant can connect. Nothing is copied out of Sedna: the assistant queries your workspace live, and each person sees only the Sedna teams they belong to.
What it can do
- Read messages and full email bodies, teams, users, contacts, job references, category tags and attachments, including authenticated download links.
- Summarise a job reference: activity, key participants, tags applied and recent traffic, in one request.
- File and classify by applying category tags to a message and linking job references to it.
- Search your mail with full-text search across sender, recipient, subject, body, dates, attachments, tags and job references. Part of the Enhanced MCP Server.
- Build Sedna apps with Canvas: the assistant can read the Canvas docs and the Sedna API reference and check your app's layout before you deploy it.
- Work with pre-fixture data: positions, cargoes and vessels, if your organisation has the Pre-fixture add-on.
It cannot send email, or delete, archive, move or edit a message. See the capability reference for the full list.
âšī¸ Enhanced MCP Server
Message search is part of the Enhanced MCP Server. Everything else on this page works on the standard product. To trial Enhanced or get pricing, speak to your account manager or customer success manager.
Before you start: one-time setup with Sedna
â ī¸ Do this first
The connector won't work until Sedna has set up sign-in for your organisation. If you add it to your assistant before then, sign-in will fail with "No Sedna tenant is configured for the domain ...".
People connect by signing in with their Microsoft work account (Google Workspace works the same way). We link your Microsoft organisation to your Sedna workspace once, and from then on everyone can connect themselves.
Who you'll need
- Someone with access to Microsoft Entra (usually IT), to give us your tenant ID and, if your organisation requires it, grant admin consent for the Sedna MCP app.
- On Claude Team or Enterprise, an organisation owner needs to add the connector for everyone.
What to send us
Email support@sedna.com. You can copy this:
Subject: Set up Sedna MCP sign-in for [company]
Please set up Microsoft sign-in for the Sedna MCP server.
- Sedna tenant: [the first part of your Sedna address, e.g. yourtenant in yourtenant.sednanetwork.com]
- Sign-in domain(s): [e.g. yourcompany.com, plus any others people sign in with]
- Microsoft Entra tenant ID: [Entra admin centre > Overview, or leave blank and we'll look it up for you to confirm]
- Teams to keep out: [Sedna team inboxes the assistant must never read, or "none"]
- Message search (Enhanced): [yes, if agreed with your account manager / no]
- Filing (apply tags and job references): [yes / no for a read-only assistant]
- Pre-fixture tools: [yes, if you have the add-on / no]
We'll set it up on our side and confirm when it's ready. You don't need to create an API credential.
While you wait
- Check email addresses match. Each person's Sedna profile must use the same email address as their Microsoft work account, or they'll get no results. Your Sedna admin can check this in each user's profile.
- Admin consent. The first time someone signs in, Microsoft asks them to approve the Sedna MCP app. If your organisation doesn't let users approve apps themselves, an Entra admin needs to grant admin consent for the Sedna MCP app, or sign in once and approve it on behalf of the organisation.
- Optional: limit who can sign in. In Microsoft Entra, open the Sedna MCP enterprise application, turn on Assignment required, and assign the users or group who should have access.
âšī¸ Can't use Microsoft or Google sign-in?
If your tool only supports custom headers, you're building a shared or automated agent, or your organisation doesn't use Microsoft 365 or Google Workspace, follow Connect with an API credential instead.
Add Sedna to your assistant
Jump to: Claude ¡ Microsoft Copilot Studio ¡ Claude Code ¡ VS Code and Cursor ¡ Other tools
Every assistant uses the same server address:
https://sednamcp.com/mcp
âšī¸ Include the /mcp
The address must end in
/mcp.https://sednamcp.comon its own will not connect.
Claude
Team and Enterprise: an organisation owner opens Organization settings â Connectors, adds a custom connector with https://sednamcp.com/mcp as the server URL, and saves. Each person then finds Sedna in their own connector list and selects Connect.
Pro and Max: each person opens Settings â Connectors, adds a custom connector with the same address, and selects Connect.
Then sign in.
Microsoft Copilot Studio
- Open your agent and go to the Tools page.
- Select Add a tool â New tool â Model Context Protocol.
-
Enter:
Field Value Server name Sedna Description Search messages, look up contacts, find job references, and access team inbox data in Sedna Server URL https://sednamcp.com/mcp - Set Authentication type to OAuth 2.0 and OAuth type to Dynamic discovery.
- Select Create, then Add to agent.
- In the tool's connection settings, choose End user credentials so each person signs in as themselves.
â ī¸ Use end-user credentials, not maker credentials
If the tool uses the maker's connection, everyone who talks to the agent sees what the maker sees, and per-person access doesn't apply.
Claude Code
claude mcp add --transport http --scope user sedna https://sednamcp.com/mcp
Claude Code opens the sign-in page on first use. No headers are needed.
VS Code and Cursor
In VS Code, create .vscode/mcp.json in your workspace. In Cursor, use Settings â MCP (same structure under an mcpServers key).
{
"servers": {
"sedna": {
"type": "http",
"url": "https://sednamcp.com/mcp"
}
}
}Your editor opens the sign-in page on first connection and handles tokens from then on.
Any other MCP-compatible tool
Enter https://sednamcp.com/mcp as the server URL. Tools that support MCP sign-in (OAuth) open the same Sedna pages and work the same way. If your tool only supports custom headers, use Connect with an API credential.
Sign in and check it works
The first time you use Sedna in your assistant:
- Approve the app. Sedna asks Allow [app name] to access your Sedna data? and shows the address your sign-in will be sent to. Select Allow if you started connecting this app yourself and recognise the address. In the same browser, you won't be asked again for that app for about six months.
- Sign in. On the Sedna MCP login page, select Sign in with Microsoft (or Sign in with Google) and use your work account. Ignore the tenant name and Client ID fields; they're for the API credential route.
- Approve Microsoft's prompt if it asks, unless your admin has already granted consent.
- You're returned to your assistant, connected.
Then ask:
"List my Sedna teams"
You should get back only the teams you belong to in Sedna. That confirms sign-in, permissions and per-person access in one call. Then try something real:
- "Summarise everything filed against job reference [your reference]."
- "Who at [company] is in our contacts?"
- "What attachments came in on [message]?"
â ī¸ Check before you act
AI assistants can be wrong, including about your Sedna data. Verify anything you'll act on commercially.
How access works
- Each person sees their own teams. Sedna matches each person's Microsoft work account to their Sedna user and returns only messages, search results, and attachments from the teams they belong to.
- Your exclusions still apply. Teams you've asked us to keep out are never returned to anyone.
- Personal inboxes are always excluded. Solo (personal) inboxes are never returned, whatever the setup.
- Leavers lose access automatically. Sedna checks each person's account with Microsoft about every hour. When an account is disabled, the connection stops working at the next check.
- No keys to share. People never see or handle an API key or Client Secret.
If you'd rather everyone in your organisation saw every shared team, ask support@sedna.com. Per-person access is the default, and the one we recommend.
What isn't limited per person
- Contacts, users and job references are visible to everyone who connects.
- Actions the assistant takes, such as applying a tag, are recorded in Sedna under your organisation's connection rather than the person. Sign-ins are recorded per person.
- People with View all teams in Sedna see only the teams they're a member of through the assistant, so they may see less there than in Sedna.
Moving from an API credential to Microsoft sign-in
If your organisation already connects with a Client ID and Secret or an API key:
- Send us the details in Before you start. We'll confirm when sign-in is ready.
- Test with a small group first: each person disconnects Sedna in their assistant, reconnects, and chooses Sign in with Microsoft. Check that they see only their own teams.
- Roll it out to everyone, then remove the old connectors and revoke the old credential in Settings â API Credentials Management (or ask support@sedna.com to revoke an API key). Until you do, anyone still on the old connection keeps tenant-wide access.
Capability reference
| What you can ask for | Tools | Notes |
| Find messages | search_messages |
Enhanced only. Full-text across sender, recipient, subject, body, dates, attachments, tags, and job references |
| Read a message | get_message |
Full HTML body, not just the summary |
| Work with attachments |
get_message_attachments, get_document_details, download_document
|
Inline images filtered out; download links are authenticated and checked against exclusions and per-person access |
| Follow a voyage, booking or deal |
get_job_references, get_job_reference_by_id, get_job_reference_messages, get_job_reference_summary
|
get_job_reference_summary Returns statistics, participants, tags and recent activity from the latest 50 messages in one call |
| Browse by classification |
get_category_tags, get_category_tag_by_id, get_messages_with_category_tag
|
Your own tag vocabulary, such as Urgent, Charter Party or Invoice |
| Look up people |
get_contacts, get_contact_by_id, get_users, get_user_by_id
|
Address book and internal users; search by name, email or company |
| Look up teams |
get_teams, get_team_by_id
|
Excluded teams and personal inboxes never appear; per-person access narrows this further |
| File and classify mail |
add_category_tag_to_message, add_job_reference_to_message
|
Only if your organisation has asked for filing to be enabled. Both are reversible in Sedna |
| Build Sedna apps (Canvas) |
canvas_overview, get_canvas_docs, get_canvas_schema, get_canvas_best_practices, validate_canvas_json, search_sedna_api_reference, get_sedna_api_endpoint_docs
|
Available to everyone. Reads Sedna's documentation, not your data |
| Pre-fixture positions and cargoes |
chartering_get_positions, chartering_get_position, chartering_get_cargoes, chartering_get_cargo, chartering_find_vessels, chartering_find_areas, chartering_get_custom_columns
|
Pre-fixture add-on only. Appears in your assistant once it's enabled for your organisation |
List tools return summarised fields with pagination to keep responses inside the assistant's context window. Use the matching get_..._by_id tool for the full record.
Troubleshooting
| What you see | What to do |
| "No Sedna tenant is configured for the domain ..." or "Microsoft sign-in isn't set up for your organisation yet" | The one-time setup isn't done for your domain yet. See Before you start, and include every domain people sign in with. |
| "The domain ... is registered to a different Microsoft tenant" | The domain doesn't match the Microsoft tenant we have on file. Send support@sedna.com your Entra tenant ID. |
| "Personal Microsoft accounts are not supported" | Sign in with your work account, not a personal Outlook or Hotmail account. |
| Microsoft says "Need admin approval" | Your organisation blocks user consent. An Entra admin needs to grant admin consent for the Sedna MCP app. |
user_not_found_in_tenant |
Your Microsoft work email doesn't match a Sedna user. Ask your Sedna admin to check the email address on your Sedna profile. |
| Connected, but empty results | You may not belong to any Sedna teams once exclusions are applied. Check your team memberships in Sedna. |
| You see fewer teams than in Sedna | Expected if you have View all teams in Sedna: the assistant uses team membership only. |
| Everyone using a Copilot agent sees the same results | The tool uses maker credentials. Switch it to end-user credentials. |
| "Sign in again with your organisation's Google or Microsoft account." | Your organisation uses per-person access, and this connection wasn't made with Microsoft or Google sign-in. Disconnect, reconnect, and choose Sign in with Microsoft. |
| "invalid_client: unknown client_id. Reconnect from your app." | Remove the Sedna connector from your assistant and add it again. |
| "Sign-in must finish in the browser it started in" | Start again from your assistant, and complete sign-in in the browser window it opens. Don't copy the link to another browser. |
| Asked to approve the app or sign in again after an update | Expected occasionally. Approve and sign in as before. |
| "Temporarily unable to check access settings. Please retry." | A temporary problem on our side. Wait a minute and retry. |
| Connects, then no tools appear | Confirm the address ends in/mcp, then restart your assistant so it re-reads the tool list. |
| The assistant says message search isn't available | Message search is part of the Enhanced MCP Server. Speak to your account manager or CSM about a trial. Meanwhile, the assistant can still browse by team, tag, or job reference. If you already have Enhanced, ask support@sedna.com to check that your connection has the Search permission. |
| The assistant says chartering or pre-fixture isn't enabled | Pre-fixture tools are a paid add-on. Speak to your account manager or CSM. |
| Truncated or partial results | Large responses are trimmed to keep the assistant responsive. Narrow the request with a date range, a team, or a tag. |
| Team or user changes not reflected | Team and user details are cached for about five minutes. Wait and retry. |
| Sign-in page won't load | Check that your network allows it sednamcp.com. If it's blocked, ask IT to allow it. |
Still stuck? Contact support@sedna.com with your tenant name, the assistant you're using, and the exact error text.
Keeping it secure
- Use Microsoft sign-in, so each person sees only their own teams and leavers lose access automatically.
- Only select Allow on the approval page if you started connecting the app yourself and recognise the address shown.
- Use Assignment required in Microsoft Entra to control who can sign in.
- Tell us about any team inboxes that must stay out of the assistant before you roll out.
- Connect only assistants your organisation has approved.
- If you also use API credentials, see Keeping it secure in the API credential article.
Comments
0 comments
Article is closed for comments.