Composway
/MCP Documentation
SupportOpen app
MCP Documentation

Getting Started

Connect Composway to your AI assistant to analyze Google Search Console and Bing Webmaster Tools data in a conversation.

The setup has four steps:

  1. Connect a search property to a Composway workspace.
  2. Add the Composway MCP server to your assistant.
  3. Sign in to Composway and approve the connection.
  4. Check the connection and ask your first search-performance question.

1. Prepare your Composway workspace

Your assistant reads the search data available to your signed-in Composway account.

Complete these steps in the Composway app:

  1. Create an account or sign in.
  2. Create or select a workspace for the site you want to analyze.
  3. Connect Google Search Console, Bing Webmaster Tools, or both.
  4. Select the Google property or Bing site for that workspace.
  5. Check that the data has started syncing before asking for performance analysis.

Connecting an account does not attach every accessible property to a workspace. Select the property or site you want to use. If you connect only Google, the assistant can report Google results but cannot compare them with Bing.

The analytics recipes read search-performance data. They do not change your Google Search Console or Bing Webmaster Tools properties.

2. Add the server to your assistant

Every client uses the same Composway server URL.

https://mcp.composway.ai/mcp

Composway uses Streamable HTTP, the connection method for this remote MCP server. It uses OAuth 2.1 for sign-in, so you authorize the connection in your browser rather than paste an API key into a configuration file.

Choose your client from the following list:

  • Claude web and desktop apps.
  • ChatGPT.
  • Claude Code.
  • Codex.
  • Cursor.
  • VS Code.
  • Zed.
  • Other MCP clients.

Menu labels and access depend on your client version, plan, and organization settings. Update your client if it does not support remote MCP servers and OAuth sign-in.

Add Composway as a custom remote connector.

  1. Open Customize → Connectors.
  2. Choose Add, then the option to add a custom web connector. Some versions label this Add custom connector.
  3. Enter Composway as the name and paste the server URL.
  4. Review the detected authentication settings. Choose a sign-in option, not No sign in.
  5. Finish adding the connector. Sign in to Composway and approve the requested access.
  6. Enable Composway for the conversation if your client asks you to select connectors.

For a Team or Enterprise organization, an owner or another authorized administrator must add the connector in Organization settings → Connectors first. Members then connect individually with their own Composway accounts.

See Claude's connector setup guide if the controls differ from these steps.

Add the server and complete OAuth sign-in as separate steps.

Run these commands in your terminal:

Terminal
bash
codex mcp add composway --url https://mcp.composway.ai/mcpcodex mcp login composway

Complete the browser sign-in when Codex opens it. Adding the URL does not complete authentication.

You can also add this entry to ~/.codex/config.toml:

toml
[mcp_servers.composway]url = "https://mcp.composway.ai/mcp"

Use .codex/config.toml for a trusted project's configuration. Run codex mcp login composway after adding the entry by hand.

Run this command to check configured servers:

codex mcp list

See Codex's MCP guide for configuration details.

3. Check the connection

Check both assistant authentication and the site's data connection before asking for analysis.

Use this prompt after adding Composway:

Check my Composway connection. Call get_server_status and confirm that I am authenticated. List the accessible sites with list_sites. For [your domain], call get_connection_status and show the resolved workspace, selected Google property, selected Bing site, and last sync time. Tell me if a property is not attached or if a different workspace was selected. Do not create workspaces or change settings.

A successful check returns the following information:

  • The server version, tool schema version, and authenticated identity.
  • The properties and sites visible through your connected accounts.
  • The workspace and selected property or site used for your domain.
  • The last sync time.

A connected Google or Bing account does not prove that a property or site is selected for the workspace. Check the selected property and selected site fields before interpreting missing performance data.

4. Ask your first question

Start with a site snapshot and a short trend before requesting a larger investigation.

Use this prompt to review recent performance:

Review [your domain]'s web-search performance for the latest 28-day window available. State the exact dates and measured coverage. Compare it with the preceding 28 days using get_site_snapshot, then use get_performance_trend to show when performance changed. Keep Google and Bing separate. Explain missing data and finish with three follow-up questions. Do not run paid tools or change settings.

Use Use Cases for recipes on reporting, traffic losses, page-two keywords, CTR reviews, content refreshes, and other search-analytics work.

If the setup does not work

Use these checks to separate sign-in problems from missing site data.

The server is configured but unauthenticated

Complete the OAuth flow for the client you added. In Claude Code, use /mcp. In Codex, run codex mcp login composway.

Reconnect if your authorization expired. Do not paste passwords or access tokens into the chat or configuration as a workaround.

A site is listed but analysis cannot read it

Check whether the property is attached to a workspace available to your signed-in account. Select the intended property in Composway and check the sync status.

Confirm the exact Google property. A domain property and a URL-prefix property can cover different pages. Stop and check the workspace selection if the assistant resolves a different workspace than expected.

Google works but Bing is missing

Check the selected Bing site for the workspace. Connecting Bing account credentials alone is not enough.

Missing Bing data is not zero traffic. Image and video requests return Google data only because Bing does not expose those search-vertical splits through these tools.

The assistant does not see the tools

Enable Composway for the chat and refresh the client's tool list. Check your organization permissions if the client blocks custom servers.

Call get_server_status at the start of each session. If the schema version changed, refresh tool discovery and read the current tool definitions before continuing. Some clients require an app refresh or administrator update for published tool lists.

A large analysis times out

Start with one site, a shorter series, or fewer report sections. Expand the request after the smaller call succeeds. Keep failed sections visible rather than presenting partial results as a complete report.

On This Page