Skip to main content

Portals

The Society does not operate in isolation. It maintains portals.

The Agenthood connects to external systems through Portals — MCP (Model Context Protocol)
servers that give members a window into outside worlds.
Issue trackers, monitoring systems, communication platforms, data stores.
The Society steps through. The Society steps back. Nothing leaks.


Available Connectors

ConnectorWhat members can doPrimary user
github.mdRead/create issues, PRs, releases, labelsThe Herald, The Doorman, The Scribe
linear.mdRead/update tickets, create branches from issuesThe Architect, The Herald
jira.mdRead/update tickets, create branches from issuesThe Architect, The Herald
slack.mdPost briefings, alerts, and release announcementsThe Herald, The Doorman
sentry.mdRead error events, link to commits and PRsThe Debugger, The Auditor

How Connectors Work

Each connector is an MCP server configuration. Members call connector tools
through the standard tool interface — they do not call external APIs directly.

The credential proxy handles authentication — members never see raw API keys.


Runtime Integration (planned)

With the TypeScript runtime, portal tools are available as injectable functions
injected directly into member agents — no manual MCP server configuration
required for supported portals.

The tools_for(member_name) method on each portal class enforces the
Primary Members scope column from the portal's Available Tools table,
so The Herald only receives release tools and The Reviewer only receives
PR read/comment tools.

This is planned for a future milestone (see src/portals/ — directory does not exist yet).


Adding a Connector

  1. Create a new [service].md file using the template below
  2. Configure the MCP server in your agent runtime's settings
  3. Add the connector to AGENTS.md so all members know it exists
  4. Update the table above

Template:

# Connector: [Service Name]

## What it provides
What data and actions members can access through this connector.

## Available tools
List of MCP tool names and what each does.

## Which members use it
Which Society members need access and why.

## Setup
How to configure the MCP server for this connector.

## Notes
Rate limits, authentication requirements, known limitations.