MCP server: One MCP server.

Common Elements

@commonelementsRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

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

Legal researchv1.1.0MITShell
Freeno charge per call

One address for any MCP client. You sign in at commonelements.com once, after adding it.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

What it asks for at sign-in

Access toReadChange
AssociationsNot stated: associations
RiskNot stated: risk
ComplianceNot stated: compliance
StatutesNot stated: statutes
LicensesNot stated: licenses
Vendors
ProfessionalsNot stated: professionals
Account
Forum
Rfp
Messages
Connections

From the sign-in at commonelements.com, as the endpoint publishes it. You approve it there.

Tools

None listed · checked 11 Oct 2026

Odel could not list its tools without signing in.

Try it in the Inspector
README3 min read

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-plugins
claude 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: hello@commonelements.com.

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-elements
    claude 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.

Similar modules

Browse Legal research