Connect to the MCP Server

Follow these steps to connect your MCP client over SSE.

1 Build your SSE URL

Point your MCP client at the /sse endpoint with these query parameters:

Param	Description
`email`	Your account email (shared across all agents in this session)
`es_url`	Default Everyday Series instance URL (e.g. `https://app.everydayseries.ai`), shared unless an agent overrides it
`serverId`	Any unique ID for this connection (e.g. a UUID)
`agents`	JSON array of every agent for this session — see step 2. The first entry is the active one at connect time.

Legacy alternative for a single agent: pass es_team_slug and user_es_key directly instead of agents. Still supported, but agents is recommended — it's the only way to seed more than one agent, and works fine with just one entry too.

2 Example URL

One agent, using agents:

GET {origin}/sse?email=you@example.com&es_url=https://app.everydayseries.ai&serverId=my-client-01&agents=%5B%7B%22slug%22%3A%22your-team-slug%22%2C%22es_key%22%3A%22es-xxxxxxxxxxxx%22%7D%5D

Decoded agents: [{"slug":"your-team-slug","es_key":"es-xxxxxxxxxxxx"}]

Two agents, seeded at connect time (no add_session_agent call needed):

GET {origin}/sse?email=you@example.com&es_url=https://app.everydayseries.ai&serverId=my-client-01&agents=%5B%7B%22slug%22%3A%22team1%22%2C%22es_key%22%3A%22es-xxxxxxxxxxxx%22%2C%22label%22%3A%22Team%201%22%7D%2C%7B%22slug%22%3A%22team2%22%2C%22es_key%22%3A%22es-yyyyyyyyyyyy%22%2C%22label%22%3A%22Team%202%22%7D%5D

Decoded agents: [{"slug":"team1","es_key":"es-xxxxxxxxxxxx","label":"Team 1"},{"slug":"team2","es_key":"es-yyyyyyyyyyyy","label":"Team 2"}]. The first entry (team1) is active immediately; use switch_agent to switch to team2. Each entry needs slug and es_key; es_url, email, and label are optional per-entry overrides.

Replace {origin} with this server's base URL.

3 Configure your MCP client

Most MCP clients that support SSE transports just need the full URL above as the server endpoint. For example, in a JSON-based config:

{
  "mcpServers": {
    "everyday-series": {
      "url": "{origin}/sse?email=you@example.com&es_url=https://app.everydayseries.ai&serverId=my-client-01&agents=%5B%7B%22slug%22%3A%22your-team-slug%22%2C%22es_key%22%3A%22es-xxxxxxxxxxxx%22%7D%5D"
    }
  }
}

4 Verify the connection

Check active sessions any time at /sse/status, or browse the full API reference at /api-docs.

5 What you get

Once connected, your session includes:

Dynamic flow tools — one per published flow in your team, fetched live.
Everyday Series platform tools — series/flows, tags, members & invites, agent settings, tools catalog, writer documents, organizations, AI provider keys, profile, developer API keys, and Appwrite sites/databases (~65 tools).
web_search / scrape_url — general-purpose web search and URL scraping.
list_skills / get_skill — usage guides for which tool to call for a given task. Call list_skills to see topics, then get_skill for the full guide on one.
Multi-agent tools — add_session_agent, list_session_agents, switch_agent, remove_session_agent. Work with more than one team/agent in a single session and switch which one is active mid-conversation, no reconnect needed.

Working with more than one team? Either call add_session_agent mid-conversation with its slug and API key, then switch_agent to make it active — or seed them all at connect time with the agents URL param (step 2) so they're ready from the start. All tools (including dynamic flow tools) automatically follow the switch.