MCP Server

Automate Symphony Messaging tasks, notify teammates, and use Symphony Messaging chat as context in Claude, Gemini or any other MCP client.

Overview and capabilities

Symphony's MCP server connects Symphony Messaging to MCP-compatible AI clients.

You can automate tasks and notify teammates directly from an AI assistant or use Symphony Messaging conversations as context for prompts in Claude, Gemini or any other MCP client.

It gives AI clients a standard way to discover tools, inspect inputs, and run actions in Symphony Messaging, reducing custom integration work and making tool-driven workflows easier to build, test, and govern.

Security, premissions and data governance

Symphony's MCP server is built on Symphony applications and on-behalf-of (OBO) permissions.

It follows the same security model as authenticated apps in Symphony Messaging. For context, see Planning Your App, App Authentication, and OBO Authentication.

Each user gets a dedicated OBO session when they use the server.

This gives organizations strong control and traceability:

• Users never access more data than they can already access in Symphony Messaging.

• Room membership, history sharing, and information barriers are enforced by default.

• Actions such as room creation or message sending are recorded in audit trail and content export as actions performed by the MCP server on behalf of the user.

This ensures the assistant remains aligned with existing permission boundaries within Symphony Messaging, and provides Admins with an extra control layer through application permissions.

Admins can use app permissions as an overlay to restrict which MCP actions are available. For example, they can allow read-only workflows and block authoring actions such as sending messages or creating rooms.

Service activation

Symphony's MCP server must be enabled before you can use it.

Symphony's MCP server is an add-on to Symphony Services. It is subject to additional charges.

Contact the Symphony team to enable the service in your environment before you can start using it.

Once the service is enabled, you can connect Symphony's MCP server to any MCP-compatible AI client, including Claude, ChatGPT, Mistral, and other AI agents that support MCP protocol.

Connect with Symphony's MCP

Symphony's MCP server is a remote server that you can start using immediately with zero deployment required. Connect your MCP client, complete the authorization flow, and start prompting.

The MCP server is exposed through your tenant-specific URL, for example https://xxx.symphony.com/mcp-server/mcpapp/mcp.

Symphony's MCP Server implements secure authorization using OAuth 2.1.

A dedicated setup guide will soon be available for each MCP client. Don't hesitate to contact the Symphony's support team at [e-mail] if you need help for your first setup.

Tool reference

add_user_to_room

Adds a new member to an existing room.

change_my_presence

Change my presence status: available, busy, be right back, in a meeting, out of office. The presence status that was set is returned.

create_chat

Creates a direct chat between you and another Symphony Messaging user. A direct chat or direct message is different from a chat room, it's unique and immutable. The newly created direct chat is only returned if it was never created before, otherwise, the existing chat is returned.

create_room_with_user

Creates a new room and adds the user to it.

download_attachment

Downloads an attachment from a conversation.

It returns the file content as base64.

get_financial_instrument_details

Get details of a specific financial instrument identified by its identifier.

list_allowed_file_types

Lists the file types allowed for attachments.

list_attachments

Lists attachments in a conversation.

list_messages

Returns messages and message metadata for a conversation.

By default, it retrieves one day of history. The maximum period is seven days.

list_room_members

Retrieves the list of members for a specific Symphony Messaging chat. Provides details for each member, including their join date and whether they are a chat room owner.

lookup_user

Searches users by emails OR Symphony Messaging user IDs (exclusive).

remove_message

Removes a given message, identified by its identifier, from the conversation it belongs to.

remove_user_from_room

If requesting user is allowed, removes a user from a given Symphony room.

room_search

Searches for rooms that match a query or topic.

search_messages_by_meaning

Searches for messages using a natural-language semantic query. Unlike a keyword search, the query is interpreted by meaning rather than matched literally.

search_financial_instruments

Searches for financial instruments matching the supplied query (e.g. a ticker).

search_user

Searches the Symphony directory for users.

Use this tool when you need to find people, bots, or distribution lists.

see_user_presence

Shows the presence status of a given user identified by their Symphony Messaging identifier. If the user belongs to an external organisation then it must be specified, otherwise a user of my organisation is assumed.

send_message

Sends a message to a conversation identified by its stream.

If the message is sent successfully, the response includes message metadata such as its identifier and timestamp.

update_message

Updates a given message, identified by its identifier, in the conversation it belongs to, identified by its identifier. The existing message is fully replaced by the new message. The new version of the message is returned.

update_room

Changes the attributes of a given room, including its name, the pinned message and all attributes available for the room creation tool, except changing public/private. Returns the details of the updated room.

who_am_i

Returns the identity of the current user.

This includes details such as full name, email address, and title.