This article helps you fix common problems connecting an AI assistant to the Elements MCP (Model Context Protocol) server, or using it once connected.

Find the symptom you're seeing below. Most connection problems come from one of three causes:

If you can't connect to the Elements MCP server, or no Spaces appear when you sign in, the Space you want usually isn't licensed for the MCP server yet. MCP is included in Advanced Metadata Management, or in Core Metadata Management with the Agentic Org Management add-on, and Elements enables it per Space. If a Space you expect to see is missing from the consent screen, it isn't licensed yet; once it is, connect again and it will appear.

An Elements MCP endpoint that works for one Org may not work for another, because Elements runs in more than one location. Log into Elements, check the URL in your browser, and use the matching endpoint from the table in Connect your AI assistant to the Elements MCP server. Don't choose an endpoint based on where you or your company are located.

If signing in to Elements keeps looping, clear your assistant's saved Elements authorization and connect again. In most assistants this is in the same menu where you added the connection: look for 'Disconnect' or 'Remove server', then reconnect.

A 401 or 405 error when you open the Elements MCP endpoint in a browser is expected and doesn't mean the service is down. The endpoint only accepts signed-in POST requests, which your assistant sends automatically. A browser sends a GET request instead, so you see 401 Unauthorized if you're not signed in, or 405 Method Not Allowed if you are. Connect through your AI assistant instead of opening the URL directly.

If your Elements account belongs to more than one Space, Elements asks you to choose which Spaces the connection can use when you first sign in. To change that choice later, revoke the connection and reconnect; see Elements MCP server security, data access and admin controls. You can also ask your assistant to switch between your approved Spaces at any time, for example "Switch to the example project Space."

When no Space is active, Elements uses your eligible default Space if you approved it for the connection, or else the one eligible Space you approved if there is exactly one. Otherwise, the call returns active_space_required. Ask your assistant to switch to one of your approved Spaces, or reconnect and include your default Space.

If none of the Spaces you approved can be used, every request is refused except disconnecting. A Space named explicitly in a request must also be authorized for the connection and enabled for the MCP server.

A 'too many requests' or 'server busy' message means a rate limit was reached. Each connection is rate-limited and can run up to 20 requests at the same time, and the server as a whole may reply 'server busy' under heavy load. Diagram changes and exports (manage_diagram, create_map, create_map_from_template, import_diagram, export_diagram) run one at a time on each server, so one sent while another is being saved may also get 'server busy'.

Your assistant reports this as rate_limited, too_many_concurrent_requests or server_busy, each with the number of seconds to wait. Wait the full time before trying again: retrying sooner won't work, but it won't extend the pause either. Then ask your assistant to make fewer requests in parallel.

Large-result behavior depends on the tool. Six tools return rows as downloadable part files, while other read tools answer inline and may move oversized values to a file or shorten a list with a continuation hint. If a request times out, narrow the search, filter or item selection, for example to fewer items, one object or one metadata type, and try again. See the Elements MCP server tools reference.

The tool list depends on the plan and licence flags of your authorized Spaces. Role requirements, such as Space admin or Author, are checked when you call a tool; a call without the required role is refused with access_denied. After a licensing change, start a new conversation so your assistant picks up the updated tool list.

If your connection covers several Spaces, a tool available through one Space can return feature_not_enabled for a missing plan or feature flag, or access_denied for a missing Elements role or resource access. A feature-flag refusal may tell your assistant to check Spaces with get_space_context and switch with set_active_space; role and resource refusals don't always include that hint.

What common refusal messages mean:

The Elements MCP server tools reference lists what each tool needs.

Copilot Studio shows 'The client_id is not registered' (invalid_client) when nobody signed in to the connector within 24 hours of creating it, so Elements discarded its registration. Delete the MCP server from your agent's 'Tools', add it again, and create a connection and sign in straight away. Once one sign-in succeeds, the registration is permanent.

ChatGPT rejects an Elements plugin upload as a duplicate when the plugin name is still held on your account, even after you uninstalled it. Log out of ChatGPT and back in, then upload again. If ChatGPT still refuses, the name is held by an earlier upload that needs uninstalling first.

If the Elements plugin, its skills or its tools don't appear in ChatGPT after you upload or connect it, log out of ChatGPT and back in to refresh the plugin list.

If Codex doesn't list the Elements skills, run /skills and turn on the ones you need. Invoke a skill with $, for example $elements-spaces.

If Claude Desktop or claude.ai shows ${user_config.apiHost} in the Elements connector URL, replace that placeholder with your Elements host, for example api.q9elements.com, so the URL reads https://api.q9elements.com/api/v1/mcp. See the Claude Desktop and claude.ai steps in Connect your AI assistant to the Elements MCP server.

Removing Elements from your assistant's settings stops that assistant using it, but the connection stays valid in Elements until its refresh token expires, 30 days after its last refresh; a connection used at least monthly stays signed in. To end it immediately, open your Elements profile, select the 'Connected apps' tab, find the connection and click 'Revoke'. Space administrators can also remove their Space from a connection. Both take effect immediately.

No. The MCP server reads from the same Elements data your account can already access; the connection itself creates and stores no additional copy of your data.

Any assistant whose MCP client supports remote MCP servers with the MCP standard's secure sign-in (OAuth 2.1 with PKCE). Elements has been tested with Claude (CLI and Cowork), Codex CLI, ChatGPT (Work) and Cursor.

If none of these steps fixes your Elements MCP problem, contact Elements support with the name of your AI assistant, the endpoint you used, and the exact error message. Elements support can also investigate a connection's activity from the audit logs.