# local.foundation

> A research and infrastructure organization studying how communities, startup
> ecosystems and networks coordinate — and the platform where those communities
> run themselves: members, events and onboarding.

Software can talk to the platform directly. An MCP server exposes the
communities an operator manages, plus a consent-based member-onboarding write
surface. No destructive tools.

## Start here

- [MCP server reference](https://local.foundation/developers/mcp): endpoint,
  transport, authentication, all nine tools, scoping, rate limits and errors.
  The complete specification for an agent, readable without an account.

## Machine-readable entry points

- **MCP server: `https://local.foundation/mcp`** — the primary agent interface.
  JSON-RPC 2.0 over MCP Streamable HTTP, protocol version `2025-03-26`.
  Authenticate with `Authorization: Bearer <personal API key>`.
- **OpenAPI spec: `https://local.foundation/api/docs/openapi.json`** — the REST
  surface, kept as the fallback for clients that cannot speak MCP.
- **OIDC discovery: `https://local.foundation/.well-known/openid-configuration`**
  — for the OAuth authorization-code + PKCE flow.

## Getting a credential

Create a personal API key at https://local.foundation (Profile → API Keys).
Community-scoped tokens are rejected by the MCP server — use a personal
credential. The agent authenticates as the developer who owns the key, and
every tool then acts with that person's managed-community reach.

## The tools

Reads: `community_profile`, `list_community_events`, `get_event`, `get_member`,
`search_onboarding_communities`.

Writes: `create_member` (the platform emails the set-password link — no
password transits the agent), `set_member_attributes`, `add_member_to_community`
(manager-authority hand-off), `set_onboarding_opt_in`.

## Limits and rules

- Every tool is scoped to the communities the caller manages. Anything outside
  that reach answers `not found`, never `403` — the server does not leak which
  ids exist.
- Member records are provenance-scoped to the agent that created them.
- Writes: `create_member` 20/agent/hour, `add_member_to_community`
  60/agent/hour, `set_member_attributes` 120/agent/hour. The `/mcp` endpoint
  allows 120 requests/minute per IP.