Skip to main content

Using the Walls.io Echo MCP Server

How to integrate Walls.io Echo into Claude and ChatGPT using our MCP Server

Written by Michael Kamleitner

Connecting AI Assistants to Walls.io Echo (MCP Server)

Walls.io Echo ships with an MCP server — a connector built on the Model Context Protocol, the open standard that lets AI assistants like Claude and ChatGPT securely work with your data. Once connected, your assistant can read your campaigns and analytics, answer questions about them in plain language, and even create or update campaigns for you.

There is nothing to install on a server and no API keys to copy around: you paste one URL into your AI assistant, approve access in your browser, and you're connected.

💡 Hint: the main URL for our MCP server is https://mcp.echo.walls.io/mcp

What You Can Do With It

Once connected, just ask in plain language. A few examples:

  • Analytics Q&A"How did the spring conference campaign perform last week compared to the week before? Where did the clicks come from?" The assistant pulls the summary, timeseries, and platform/country breakdowns and answers with real numbers.

  • Instant reports"Summarise all my active campaigns in a table: pageviews, shares, clicks, viral boost, and conversions for the last 30 days. Highlight the best and worst performer."

  • Find your top advocates"Who are the 10 people whose shares of our product-launch campaign generated the most clicks? Draft a thank-you message for each."

  • Data-driven advice"Looking at the daily timeseries, on which weekday does sharing peak? When should we schedule the reminder email?"

Adding Walls.io Echo to Claude (Desktop App or claude.ai)

  1. Open Settings → Connectors (in the Claude desktop app or on claude.ai).

  2. Click Add custom connector.

  3. Paste the connection URL: https://mcp.echo.walls.io/mcp

  4. Confirm — a browser window opens Walls.io Echo's authorisation screen. Sign in with your Echo account and approve access.

  5. Done. In any new chat, Claude can now use the Echo tools — try asking "List my Echo campaigns."

Note: Custom connectors require a paid Claude plan. On Team/Enterprise plans an admin may need to enable custom connectors for the workspace.

Adding Walls.io Echo to Claude Code (Command Line)

If you work in the terminal, add Echo with a single command:

claude mcp add --transport http wallsio-echo https://mcp.echo.walls.io/mcp

Then, inside a Claude Code session, run /mcp and select echo-walls to authenticate — your browser opens the same authorisation screen, sign in and approve. From then on, Claude Code can query your campaigns and analytics right from your terminal.

Adding Walls.io Echo to ChatGPT

Custom MCP connectors in ChatGPT require a paid plan and developer mode:

  1. Open Settings → Connectors (on the web, chatgpt.com).

  2. Under Advanced settings, enable Developer mode.

  3. Back in Connectors, click Create and fill in:

    • Name: Walls.io Echo

    • MCP server URL: https://mcp.echo.walls.io/mcp

    • Authentication: OAuth

  4. Save — ChatGPT redirects you to Echo's authorisation screen. Sign in and approve access.

  5. In a new chat, enable the Echo connector (via the tools/plus menu) and start asking questions about your campaigns.

Note: On Business/Enterprise plans, a workspace admin may need to add the connector before members can use it. OpenAI is still evolving this feature, so the exact menu names can shift over time.

How Authentication Works

The Walls.io Echo MCP server uses OAuth 2.1 — the same mechanism "Sign in with Google" uses:

  • You never copy or paste a token; your AI assistant registers itself and sends you to Echo's own sign-in screen.

  • You approve access once per assistant; you can keep working until you revoke it.

  • The connection only ever accesses campaigns owned by your Echo account — no other user's data is visible.

To see or disconnect connected assistants at any time, go to Dashboard → Settings → Connected apps and revoke access there.

Available Tools

Your assistant chooses the right tool automatically — you never call these yourself — but for reference, the server currently offers:

Tool

What it does

List campaigns

All your campaigns with their key stats

Get campaign

Full detail for one campaign (by id or slug)

Campaign analytics

Lifetime or date-ranged totals: pageviews, shares, clicks, viral boost, conversions

Analytics timeseries

Daily metric values for trend questions

Analytics breakdown

Metrics split by platform, country, and more

Campaign shares

The recent-shares list, including per-sharer clicks and conversions

Create campaign

Set up a new campaign

Update campaign

Change an existing campaign's settings

Delete campaign

Permanently remove a campaign

The always up-to-date tool list with all parameters is published at https://mcp.echo.walls.io.

Good to Know

  • Deleting is permanent. The delete tool is marked as destructive, so assistants ask for confirmation first — but a deleted campaign cannot be restored. Consider it carefully before approving.

  • Date ranges are optional. If you don't mention one, analytics answers cover the campaign's lifetime (summaries) or the last 30 days (timeseries and breakdowns).

  • Reference campaigns naturally. You can use a campaign's name in conversation — the assistant resolves it to the right campaign via its id or slug.

  • Prefer plain REST? Everything the MCP server exposes is also available through the Walls.io Echo API.

If you have further questions, don't hesitate to contact the support team via chat or support@walls.io!

Did this answer your question?