Common Elements

com.commonelementsPublished by commonelements.comOfficial publisherv1.1.0Updated Oct 26, 2026

Community association records, statutes, licenses, RFPs and the change feed. OAuth or API key.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Hosted Common Elements MCP server for researching US community associations: public records, statutes, licensed vendors, RFPs and change feeds.

What you can do
  • Research HOA, condo and co-op associations from state registries and other public records, with source attribution on each response
  • Search US community association statutes, read section text, and run a read-only compliance scan on text you supply
  • Look up contractors and licensed firms from state licensing-board records and check licenses
  • Post work to the RFP Hub and review proposals, with drafts kept private until you confirm publishing
  • Track board, officer and management changes through the change feed
When to use it
Useful for board members, managers, attorneys and vendors who need association records, statute text, license checks or RFP workflows inside an assistant. Free access covers public-record basics; deeper sections require a paid Data plan.
Requirements
Remote streamable HTTP endpoint at commonelements.com; no local package. Requires a Common Elements account signed in via OAuth (an API key is also mentioned). Claude users can install the plugin marketplace or add the server directly; other clients are covered on the developer page.
Before you install
Deeper data sections need a paid Data plan. Publishing an RFP is a write action that requires your confirmation; drafts stay private until then. The service stores requested account content and retains usage and action logs while the account is open. Statute and compliance output is reference information, not legal advice, and coverage varies by state and county.

Installation

In SourceWeft

  1. Open Common Elements in the dashboard and add it to a workspace.
  2. Connect the required 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/com.commonelements%2Fdata/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "common-elements": {
      "type": "http",
      "url": "https://commonelements.com/api/mcp"
    }
  }
}

README

Common Elements plugins for Claude

A plugin marketplace for Claude chat, Cowork and Claude Code from Common Elements, the information network for community associations.

PluginWhat it adds
common-elementsThe hosted Common Elements MCP server plus skills to research an association, find vendors, run an RFP, check a statute and track board and management changes

Install

For Claude chat and Cowork, add this marketplace under Customize > Plugins, install Common Elements, then connect it from the plugin’s Connectors tab. Installation is specific to your current Claude organization.

For Claude Code, in your shell:

bash
claude plugin marketplace add CommonElements/common-elements-claude-pluginsclaude plugin install common-elements@common-elements

Or inside Claude Code:

/plugin marketplace add CommonElements/common-elements-claude-plugins/plugin install common-elements@common-elements

Then run /mcp, choose plugin:common-elements:common-elements and sign in with your Common Elements account (OAuth). To receive new versions automatically, open /plugin, then Marketplaces, then common-elements, and turn on auto-update. Otherwise run claude plugin update common-elements@common-elements.

Prefer the server without the skills? claude mcp add --transport http common-elements https://commonelements.com/api/mcp. Every other client (Claude on the web and desktop, ChatGPT, Cursor, VS Code, Codex) is covered at https://commonelements.com/developers/mcp.

Codex reads the same repository: codex plugin marketplace add CommonElements/common-elements-claude-plugins.

What it does, honestly

  • Association records: HOA, condo and co-op associations from state registries and other public records. Free access returns public-record basics; deeper sections (management, officers, change feed, building safety, hazard risk) need a paid Data plan. Coverage varies by state and county, and every response says where its data came from.
  • Statutes: full-text search and section text for US community association statutes, plus a read-only compliance scan of text explicitly supplied for that purpose. Reference information, not legal advice.
  • Vendors and RFPs: contractors and other licensed firms from state licensing-board records, license checks, and the RFP Hub for posting work and reviewing proposals (drafts are private; publishing needs your confirmation). The searchable list of verified Common Elements vendor profiles is small and growing; it only includes vendors that have completed verification.
  • Common Elements complements the management and accounting software associations already use. It is not management or accounting software.

Data and privacy

Personal contact details (email, phone, mailing address) for individuals, such as board members, officers and licensees, are never returned by the MCP server. Board and officer data is names and titles from public records. The service stores requested account content and retains usage and action logs while your account is open. The plugin README describes transmission, retention and revocation. Privacy policy: https://commonelements.com/privacy. Questions: [email protected].

Releasing (maintainers)

  1. Change the plugin under plugins/common-elements/. Skills must use tool names that exist on the live server (apps/web/app/api/[transport]/_lib/ in the Common Elements app); rename a tool there and update the skills in the same release.
  2. Bump version in plugins/common-elements/.claude-plugin/plugin.json (and the Codex plugin.json beside it). The version lives only in the plugin manifests, never in marketplace.json. Users stay on the old copy until it changes.
  3. claude plugin validate . and claude plugin validate --strict plugins/common-elements must pass. CI runs both.
  4. Install from your local checkout in an isolated config and confirm the skills and the MCP server load:
    bash
    export CLAUDE_CONFIG_DIR=$(mktemp -d)claude plugin marketplace add ./claude plugin install common-elements@common-elementsclaude plugin details common-elements@common-elements
  5. Run claude plugin eval plugins/common-elements --no-publish and review the with/without results. The bundled disconnected scenarios verify safe fallback behavior; they do not replace live-tool testing through MCP Inspector and Claude, or testing on each supported surface.
  6. Open a PR and merge it after the required evidence passes. Optionally run claude plugin tag --push from the plugin directory.

Never rename a published plugin. If a rename is unavoidable, add the old name to renames in marketplace.json ({"old-name": "new-name"}). The map is append-only: never remove an entry, or users of the old name lose the plugin.

License

MIT for the files in this repository. Common Elements itself is covered by its terms.

Source: README.md at commit 1376ffa

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestOct 5, 2026
  2. v1.0.0Sep 16, 2026

Score

85% 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
  • License10 pts