Connect
Connect an AI assistant with MCP
Connect Claude, Cursor or another MCP client to Galactic Outreach on the Starter, Growth or Scale pack, so it can read your campaign's graphs and results and, with a key allowed to, create and change its send schedules and lead-search schedule.
By Joan Gumban · Last updated
What is MCP?
Galactic Outreach has an MCP server. MCP, the Model Context Protocol, is an open standard for giving AI assistants tools and data from outside the chat.
It is included with the Starter, Growth and Scale packs. On the free signup credits the AI assistants page in Settings shows which packs include it, and keys cannot be made until one is bought.
Connected to Galactic, an assistant such as Claude or Cursor answers questions about your campaign from its real numbers and, if you let it, looks after its schedules. What it reads is numbers and labels only: no lead, recipient or email address ever leaves.
Sources
1. Make a key
In Galactic, open Settings from the sidebar, choose AI assistants, then New key. Name it after where it will live, so you know which one to revoke later.
Tick Allow automation changes only if the assistant should be able to change schedules. Copy the key when it appears: it is shown once, and only a fingerprint of it is kept.
2. Add Galactic to your assistant
Pick your assistant and replace gx_… with your key. Every one points at the same address, with the key sent as a bearer token.
claude mcp add --transport http galactic https://galacticoutreach.com/api/mcp \
--header "Authorization: Bearer gx_…"- Clients that connect only by signing in with OAuth, such as custom connectors on claude.ai, cannot use a key yet.
3. Restart and ask
Restart the app, or start a new session in Claude Code, so it loads the server. Then ask it something about your campaign. If it cannot connect, check the key has not been revoked in Settings and that the campaign is on Starter, Growth or Scale: a request without a valid key, or from a campaign on neither, is refused.
Usage
Ask in plain words. The last two change schedules, so they need a key with automation access.
- How did sending go over the last two weeks?
- Which city has the most leads left?
- What is stopping the send right now?
- Is my bounce rate safe?
- Pause the send schedule.
- Search for dentists in Austin every weekday at 8, then email what it finds.
What can it read and change?
Six tools read and four change the automation. Reads are counts, daily series, rates and the safety checks; anything in a result that looks like an email address is replaced before it leaves.
- get_overview
- Whether the campaign may send right now and why, queue and send totals, sends against the previous 7 days, and credits left.
- Example: “Can I send today, and how many credits do I have?”
- get_graphs
- The series behind the charts: emails sent per day, sends per day by message tier, and lead searches per day.
- Example: “How did sending go over the last two weeks?”
- get_breakdowns
- Leads queued, sent and remaining per city, industry and country, send outcomes, why leads were held back, and why sends failed.
- Example: “Which city has the most leads left?”
- get_safety_checks
- Every safety check with its result and explanation, and the verdict they add up to.
- Example: “What is stopping the send?”
- get_deliverability
- What your provider's webhook reported: delivered, bounced, complained, opened and clicked, with the bounce and complaint rates.
- Example: “Is my bounce rate safe?”
- get_automation
- Every send schedule and the lead-search schedule as saved, with their last run and outcome, the industries and cities a schedule may use, and which industries each template is for.
- Example: “When does the next send go out?”
- update_send_schedule
- Changes one send schedule, named by its id when there is more than one. Needs a key with automation access.
- Example: “Pause the dentists schedule until Monday.”
- create_send_schedule
- Adds another send schedule, with its own time and templates; each template goes to its own industries. Needs a key with automation access.
- Example: “Also send Agency intro on Tuesdays at 2.”
- delete_send_schedule
- Deletes one send schedule. Needs a key with automation access.
- Example: “Delete the Friday schedule.”
- update_search_schedule
- Changes the lead-search schedule, including whether to send to what it finds. Needs a key with automation access.
- Example: “Search for dentists in Austin every weekday at 8.”
How do schedule changes work?
An update changes only what you ask for. "Pause sending" turns the schedule off and leaves its time, days and templates as they were.
Every change goes through the same checks as the schedule forms on the Send page and Find new leads: the time, the timezone, the days, that a published template is set for an industry, and for a search, that the industry and cities are ones the search form offers. A change the screen would refuse is refused here too, with the same message.
Nothing runs at the moment of the change. The schedule fires at its next time, like one saved on the Send page, and the safety checks and your credits apply to every run.
The assistant is told that schedules act unattended and to confirm changes with you, and the update tools are marked as changing data, so Claude asks before it uses them.
How are keys kept safe?
A key belongs to one campaign and reaches nothing else. Galactic keeps only its SHA-256 hash, so a copy of the database could not be used to connect.
Revoking a key in Settings stops it on its next request. Each key shows when it was last used, so one nobody uses any more is easy to spot. A campaign can hold up to 10 keys.
A request without a valid key is refused with 401 and sees nothing.
The endpoint
Streamable HTTP, stateless, answering in JSON. Send JSON-RPC messages by POST. GET is not offered and answers 405. Protocol versions 2025-06-18, 2025-03-26 and 2024-11-05 are supported.
POST https://galacticoutreach.com/api/mcp
Authorization: Bearer gx_…
Content-Type: application/json