local.foundation

foundation.localPublished by local.foundationOfficial publisherv1.0.0Updated Oct 24, 2026

Community reads and consent-based member onboarding for local communities, over MCP.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint for local.foundation that gives an assistant read access to local community data and consent-based member onboarding.

What you can do
  • Read community information from local.foundation over MCP.
  • Onboard members into communities on a consent basis.
  • No individual tools are documented in the manifest, so the exact operations are not listed; the scope is limited to community reads and member onboarding.
When to use it
When an assistant needs to look up or work with local community information held on local.foundation, or to help bring members into a community with their consent.
Requirements
A remote streamable HTTP endpoint at local.foundation; no local package or runtime. A personal API key sent as a bearer token in the Authorization header, created under Profile → API Keys on local.foundation. Community-scoped tokens are rejected, so the key must be a personal one.
Before you install
The Authorization header carries a personal API key that grants access to your account data; keep it out of logs and shared transcripts. Onboarding members involves adding people to communities, so confirm consent before any write action. Community-scoped tokens will not work, so a broader personal key is required.

Installation

In SourceWeft

  1. Open local.foundation in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/foundation.local%2Fcommunities/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "local-foundation": {
      "type": "http",
      "url": "https://local.foundation/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 12, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.