Connect Claude to OutreachPortal

The OutreachPortal connector lets Claude, and other assistants that support MCP, read and keep your outreach record: ask questions about your season, log activities, attach evidence and see where you stand for the awards.

What you need

An OutreachPortal account, with your organisation on the Outreach or Impact plan.
A Claude plan that supports custom connectors, or any other MCP client.

Connect

The server address is the same for every organisation:

https://mcp.outreachportal.app

Claude (web and desktop)

Open Customize → Connectors and choose Add custom connector.
Name it OutreachPortal, paste the address above, and add it.
Choose Connect. Claude sends you to OutreachPortal to sign in and shows what it is asking to do. Choose Allow.

The same address and a one-click copy are in the portal under Settings → AI assistants.

Claude Code

claude mcp add --transport http outreachportal https://mcp.outreachportal.app

Then type /mcp in Claude Code and choose OutreachPortal to sign in.

Scripts

On the Impact plan a script can use the same address with an API key sent as a Bearer token. It then has the permissions of the key’s user.

Things to ask

“Give me an overview of our outreach this season.”
“Which counted activities are missing a photo or letter?”
“Log a mentoring session with the Wattle Creek FLL team yesterday, two hours, three mentors.”
“Which Impact award criteria do we have no evidence for yet?”
“What have we done with team 4788, oldest first?”
“Which entries are waiting for my approval?”

Permissions and safety

Each person connects their own. The assistant acts as you and gets your permissions, read again on every request. Change your permissions and the assistant’s change with them.
Everyone can read. Editing tools appear only for people who can edit outreach, teams, the season and files. The approval tools appear only for people who can manage approvals. Anything you cannot do in the portal, the assistant cannot do. It cannot touch settings, people, billing or other organisations.
Everything it writes is reviewed. An activity it logs starts as Pending, and an edit reopens an approved entry, even when it acts for an approver. If your organisation reviews its log, nothing the assistant writes counts towards your totals until a person approves it.
It cannot delete your record. It cannot delete activities, members or teams. The one removal it can make is a file you uploaded that nothing uses.
You stay in control. End a connection any time from your profile (admins can end anyone’s under API keys). Changing your password disconnects every assistant. If the organisation’s plan lapses, the connection pauses and returns on upgrade.
Information the assistant reads is sent to its provider. See our privacy policy.

Tools

Read (everyone)

Tool	What it does
`get_overview`	Start here: the organisation, its teams, the current season and headline totals.
`get_impact_summary`	Totals for a window: entries, hours, people reached, travel and teams helped.
`list_activities`	Activities in a window, newest first, with search and filters.
`get_activity`	One activity in full: sessions, attendees, teams, details and attached files.
`list_people`	Members with their roles and the hours and activities each has.
`list_teams_helped`	Every team the organisation helped, with how often.
`get_team_history`	Everything done with one team, oldest to newest.
`search_teams`	Find teams on the books by number or name.
`get_award_criteria`	How the record measures up against the Impact and Inspire awards.
`get_award_readiness`	Which criteria are evidenced and which are open.
`list_evidence`	Files attached to activities: letters, photos, documents.
`list_activities_missing_evidence`	Counted activities that have no photo, file or letter yet.
`list_seasons`	Seasons the organisation has logged in.
`get_logging_options`	The organisation’s own activity types and lists. Used before logging.
`get_season_goals, get_learning, get_risks`	The season’s goals, learning and risks.
`get_file`	Read a file attached to the record.

Log and edit (people who can edit)

Tool	What it does
`log_activity`	Add an activity. Waits for an approver before it counts.
`update_activity`	Change an activity. An approved entry goes back for review.
`link_activity_teams`	Add or remove teams an activity involved.
`upload_file, create_upload_url, import_file_from_url`	Attach photos and documents, by upload, by a one-time upload link, or by fetching a link.
`remove_file_from_activity, delete_file`	Detach a file from an activity, or delete a file you uploaded that nothing uses.
`add_award_goal, update_award_goal, set_criterion_ticked, save_criterion_note`	Keep the award criteria.
`add_learning_goal, update_learning_goal, update_learning_track`	Keep learning goals.
`log_risk, update_risk`	Keep the risk register.

Approve (people who manage approvals)

Tool	What it does
`list_approval_queue`	Activities waiting for an approver, or for their author to answer.
`approve_activity`	Sign an activity off so it counts.
`ask_about_activity`	Send an activity back to its author with a question.
`reply_to_question`	Answer an approver’s question on the author’s behalf.

Troubleshooting

“Plan required” or a 403. The organisation must be on Outreach or Impact. An admin can upgrade in Settings → Plans & billing.
Logging tools are missing. Your permission level must allow editing; ask an admin.
Signed out after a password change. Reconnect the connector.
The sign-in page asks for two-step verification. Finish it as usual; Claude then returns you to the consent screen.

Support

Email support@outreachportal.app. See also our privacy policy, terms of service and the API reference.