This article covers connecting an AI assistant to Sedna's MCP server with an API credential issued to your organisation. Use it when:
- Your assistant or tool can't sign in with Microsoft or Google, and only supports custom headers or a configuration file
- You're building a shared or automated agent that doesn't act as one person
- Your organisation doesn't use Microsoft 365 or Google Workspace
For most teams, Microsoft sign-in is simpler and safer: each person sees only their own teams, there are no keys to manage, and leavers lose access automatically. See Connect your AI assistant to Sedna for what the assistant can do, the capability reference, and the Microsoft sign-in setup.
How access works with an API credential
An API credential gives the assistant access to your whole Sedna tenant, within these limits:
- Personal inboxes are always excluded. Solo (personal) inboxes are never returned in message results, search results, or attachment downloads. You don't need to configure this.
- Teams you want kept private. Send the team names to support@sedna.com before you go live, and we'll exclude them server-side, including any documents attached to their messages. Exclusions always apply.
- What the credential is allowed to do. You choose the credential's permissions when you create it (below).
- Optional per-person narrowing. You can name a person in each assistant's setup, so it only sees their teams (below).
Step 1: Create the credential
-
Find your tenant name. It's the first part of your Sedna web address. If you use
yourtenant.sednanetwork.com, your tenant name isyourtenant. - Create an API credential. In Sedna, go to Settings â API Credentials Management and create a credential with the permissions below. You'll get a Client ID and Client Secret. The Secret is shown only once, so store it safely. If you don't see that page, an IT Support user needs to enable the Manage API Credentials role on your profile; see API Credential Management & OAuth Authentication for details.
- Send us any teams to exclude, as described above.
Credentials carry an expiry of up to a year and can be revoked at any time.
Permissions to grant
| API | Read | Write | Needed for |
| Message | â | optional | Reading messages and email bodies. Add Write only if you want the assistant to apply tags and job references |
| Category Tag | â | Listing your tag vocabulary | |
| Job Reference | â | Voyages, bookings and deals, and their message history | |
| Team | â | Listing teams | |
| User | â | Looking up colleagues and per-person narrowing | |
| Contact | â | Address book lookups | |
| Document | â | Attachment details and download links | |
| Chartering | â | Pre-fixture positions and cargoes. Only if you have the Pre-fixture add-on |
Leave everything else unselected. No Delete permission is needed for any Sedna MCP feature. Grant Read-only, and you have a strictly read-only assistant: the two filing tools return a permission error and nothing in Sedna changes. Message Write is a general API permission that also covers creating messages, so grant it only if you want the filing tools.
Message search also needs the Search permission, which comes with the Enhanced MCP Server. Your account manager or CSM can arrange it.
Step 2: Choose how your assistant authenticates
Every method 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.
| Method | You need | Use it when |
| Client ID and Secret (recommended) | Tenant name, Client ID, Client Secret | Your assistant supports MCP sign-in (OAuth), such as Claude, Copilot Studio, Cursor, or VS Code |
| API key | Tenant name and an API key from Sedna Support | Your tool authenticates with custom headers rather than OAuth |
The Client ID and Secret method uses OAuth 2.0. It's self-service and issues short-lived tokens that refresh automatically. An API key works equally well where that's what your tool supports: request one from support@sedna.com and store it as you would any other credential.
What you'll see with a Client ID and Secret
- 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.
- On the Sedna MCP login page, enter your tenant name, Client ID, and Client Secret, then select Connect.
- You're returned to your assistant, connected.
Optional: narrow each assistant to one person's teams
Where your assistant lets you set custom headers, add:
X-Sedna-User-Email: person@yourcompany.com
Sedna then narrows every response to the teams that person belongs to: message reads, search results, and attachment downloads alike. It stacks on top of your exclusions rather than replacing them. If the address doesn't match a Sedna user, or that user has no teams left after exclusions, the assistant gets nothing rather than everything.
â ī¸ The header is not verified
Sedna trusts the address the assistant sends; it doesn't check it against who is using the assistant. Use it where you control each person's configuration. It keeps each person's assistant to their own teams; it isn't a barrier against a tool deliberately set up with someone else's address. For verified per-person access, use Microsoft sign-in.
Step 3: Connect your assistant
Claude (web and Desktop)
- Open Settings â Connectors and add a custom connector.
- Enter
https://sednamcp.com/mcpas the server URL. - Approve the app, then enter your tenant name, Client ID, and Client Secret on the Sedna login page.
- You're returned to Claude, connected.
To use an API key, or to narrow the connection to one person's teams, see Tools that use a configuration file.
Microsoft Copilot Studio
- Open your agent and go to the Tools page.
- Select Add a tool â New tool â Model Context Protocol.
-
Fill in the server details:
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 Create a new connection.
- Approve the app, then enter your tenant name, Client ID, and Client Secret on the Sedna login page.
- Back in Copilot Studio, select Add to agent.
Dynamic discovery lets Copilot Studio configure the OAuth endpoints itself. If your environment doesn't complete discovery, contact support@sedna.com for the authorization and token URLs.
Copilot Studio via a Power Apps custom connector
Use this only if the MCP connector above isn't available in your environment, or you want to pass the signed-in user's address in the X-Sedna-User-Email header.
- On the Tools page, select Add a tool â New tool â Custom connector. You'll be taken to Power Apps.
- Select New custom connector and import the schema below.
- Enter your tenant name and API key when prompted, then select Continue.
swagger: '2.0'
info:
title: Sedna MCP Server
description: MCP Server for Sedna API integration
version: 1.0.0
host: sednamcp.com
basePath: /
schemes:
- https
consumes:
- application/json
produces:
- application/json
securityDefinitions:
api_key:
type: apiKey
in: header
name: X-Sedna-Api-Key
tenant:
type: apiKey
in: header
name: X-Sedna-Tenant
security:
- api_key: []
tenant: []
paths:
/mcp:
post:
summary: MCP Endpoint
x-ms-agentic-protocol: mcp-streamable-1.0
operationId: InvokeMCP
responses:
'200':
description: SuccessThis route uses an API key rather than a Client ID and Secret. Request one from support@sedna.com. To narrow results per person, add X-Sedna-User-Email as a further header and fill it with the signed-in user's address.
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",
"headers": {
"X-Sedna-User-Email": "you@yourcompany.com"
}
}
}
}On first connection, your editor opens the Sedna pages: approve the app, then enter your tenant name, Client ID, and Client Secret. The user-email header is optional; without it, the assistant sees every team the credential can see.
Claude Code
claude mcp add --transport http --scope user sedna https://sednamcp.com/mcp \ --header "X-Sedna-User-Email: you@yourcompany.com"
Claude Code prompts for sign-in on first use. Drop the header to give the connection access to every team. To use an API key instead, add --header "X-Sedna-Tenant: your-tenant-name" and --header "X-Sedna-Api-Key: your-api-key".
Tools that use a configuration file
For Claude Desktop's claude_desktop_config.json and similar files, use an API key. Requires Node.js.
{
"mcpServers": {
"sedna": {
"command": "npx",
"args": [
"mcp-remote",
"https://sednamcp.com/mcp",
"--header", "X-Sedna-Tenant: ${SEDNA_TENANT}",
"--header", "X-Sedna-Api-Key: ${SEDNA_API_KEY}",
"--header", "X-Sedna-User-Email: ${SEDNA_USER_EMAIL}"
],
"env": {
"SEDNA_TENANT": "your-tenant-name",
"SEDNA_API_KEY": "your-api-key",
"SEDNA_USER_EMAIL": "you@yourcompany.com"
}
}
}
}Keeping credentials in env rather than inline makes them easier to rotate. Remove the user-email lines to give the connection to every team.
Any other MCP-compatible tool
Enter https://sednamcp.com/mcp as the server URL. If the tool supports OAuth, it opens the Sedna pages automatically. Otherwise, add these headers:
| Header | Value |
X-Sedna-Tenant |
Your tenant name. Required with an API key |
X-Sedna-Api-Key |
Your API key. Required with an API key |
X-Sedna-User-Email |
Optional. Narrows results to that person's teams |
Check it works
Ask your assistant "List my Sedna teams". You should get your team names back, and if you're using the user-email header, only that person's teams. See Connect your AI assistant to Sedna for more to try and the full capability reference.
Troubleshooting
| What you see | What to do |
missing_credentials or "Unauthorised" |
Supply either a Client ID and Secret or an API key. With API keys, both headers are required, and neither can be truncated. |
ambiguous_credentials |
You've sent an API key and a Client ID and Secret. Use one or the other. |
invalid_tenant_format |
Use the tenant name only: letters, numbers, hyphens or underscores. Not the full URL. |
user_not_found_in_tenant |
The address in X-Sedna-User-Email doesn't match a Sedna user. Check it against the user's Sedna profile, including their SSO address. |
| "Sign in again with your organisation's Google or Microsoft account." | Your organisation has switched to per-person Microsoft or Google sign-in. Reconnect and choose Sign in with Microsoft, or ask your IT admin. |
| "invalid_client: unknown client_id. Reconnect from your app." | Remove the Sedna connector from your assistant and add it again. |
| Empty results, but the connection works | If you're using the user-email header, that person may have no teams left once exclusions are applied. Check their team memberships in Sedna. |
| 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. If you already have Enhanced, check that the credential has the Search permission. |
| The assistant says chartering or pre-fixture isn't enabled | Pre-fixture tools are a paid add-on, and the credential needs Chartering Read. Speak to your account manager or CSM. |
| Permission errors on some requests | Your credential may not have the permissions in the table above. Check it in Settings â API Credentials Management. Permissions can't be edited after creation, so create a new credential if needed. |
| Stopped working after months | Credentials expire after up to a year. Check the credential's status in Settings â API Credentials Management and create a replacement if it's expired. |
| Was working, now "invalid session" | Disconnect and reconnect the integration to sign in again. |
| 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. |
| Login page won't load | Check that your network allows it sednamcp.com. If it's blocked, ask IT to allow it. |
npx or Node not found |
Install Node.js, or connect with your Client ID and Secret instead, which needs no local tooling. |
Still stuck? Contact support@sedna.com with your tenant name, the assistant you're using, and the exact error text.
Keeping it secure
- Prefer Microsoft sign-in wherever your people use Microsoft 365.
- Grant only the permissions in the table above, and no Delete permissions.
- Where you can set headers, narrow each person's assistant to their own teams with
X-Sedna-User-Email, and remember it isn't verified. - Treat a Client Secret or API key like a password. Don't paste it into shared documents or commit it to a repository.
- Create a separate credential per assistant, so you can revoke one without affecting the others.
- Only select Allow on the approval page if you started connecting the app yourself and recognise the address shown.
- If a credential may be exposed, revoke it in Settings â API Credentials Management, or contact support@sedna.com for API keys.
Comments
0 comments
Article is closed for comments.