Skip to main content

MCP: Connecting Claude to Elate

Connect Claude to Elate.

Connect Claude to Elate using our Model Context Protocol (MCP) server to securely access your organization's strategic data directly within Claude. Once connected, you can ask Claude questions about your strategic plan, objectives, outcomes, tactics, and more without leaving your conversation.

Note: The steps below reflect the current Claude experience on a Personal (Free) plan. Depending on your Claude plan or workspace configuration, some screens or labels may vary slightly.


Before You Begin

Before connecting Claude to Elate, ensure the following:

  • Your Elate organization has the API feature enabled in Elate.

  • You have an MCP Server URL.

  • You have a Client ID and Client Secret. These are provided by your Elate Account Manager and are unique to the integration.


Create a Custom Connector

  1. In Claude, open Settings.

  2. Select Connectors.

  3. Click Add and then Add Custom Connector in the upper right-hand corner.

4. Enter a name for your connector (for example, Elate).

5. Paste your MCP Server URL into the connector URL field. For Elate, this is https://mcp.goelate.com/mcp

6. Enter your Client ID and Client Secret. Both fields can be provided by your Elate Account Manager.

7. Save the connector.

After saving, Claude will contact the Elate MCP server and begin the OAuth authentication flow.


Authorize the Connection

After the connector has been created:

  1. Click Connect.

2. You'll be redirected to Elate's OAuth authorization page.

3. Review the requested permissions.

4. Click Approve to authorize the connection.

The connection uses your Elate user account, meaning Claude can only access the data and permissions already available to you in Elate.

After authorization is complete, you'll be redirected back to Claude, where the connector will display as Connected.


Review Available Tools

Once connected, Claude displays the tools available through the Elate MCP server. Depending on your organization's configuration, these may include tools for:

  • Listing objectives

  • Viewing goals

  • Retrieving tactics

  • Accessing strategic plan information

  • Querying other strategic planning data

Choose Always Allow for these tool permissions so thatClaude won't ask for permission each time it accesses Elate.


Start Using Elate in Claude

Once connected, you can ask Claude questions naturally about your organization's strategy.

For example:

  • Tell me about my current fiscal year strategic plan.

  • List our current objectives.

  • What goals are associated with this objective?

  • Which initiatives appear to be at risk?

When Claude determines that your question requires information from Elate, it automatically uses the tools exposed by the MCP server to retrieve the appropriate data before generating its response.

Exactly which tools Claude uses depends on your prompt and how Claude determines it can best answer your question.


Manage Your Connection

You can manage your connector at any time by returning to Settings > Connectors.

From there, you can:

  • View your connection status

  • Review the available tools

  • Disconnect the integration if you no longer want Claude to access your Elate workspace


Troubleshooting

I don't see the option to add a custom connector.

Connector availability varies by Claude plan and workspace configuration. If you don't see the option, check whether your Claude plan supports custom connectors.

The connection isn't working.

Verify that:

  • The API feature is enabled for your Elate organization.

  • Your MCP Server URL is correct.

  • Your Client ID and Client Secret were entered correctly.

  • You completed the OAuth authorization flow.

Why does Claude ask for permission to use Elate tools?

By default, Claude may ask for permission before using tools provided by the MCP server. You can choose Always Allow if you trust the Elate integration to reduce future prompts.

What data can Claude access?

Claude can only access data that your authenticated Elate user account already has permission to view. It does not receive any additional permissions through the integration.

Did this answer your question?