Integration

Your tools can read the governed record. They cannot change it alone.

An agent working on your behalf should be able to read board resolutions, risks, actions, pipeline and the rest of the governed record, the same way a person does today, without copy-pasting context into a chat window.

Boardverse gives your tools that access through a standards-based front door, and keeps every write behind the confirmation gate.

MCP server

A thin, standards-based front door onto the platform's existing access boundary. One tool per module, read-only, scoped to the same Personal Access Token a Founder already generates from Settings. No new credential type, no OAuth flow. Included in every seat at no extra charge.

Personal Access Tokens

Module-scoped and access-logged. The same token a Founder generates today is the one their agent uses.

The write boundary

A connected tool can submit, but nothing it submits is trusted until a different named person confirms it. Writes land Pending. The submitting identity is blocked from self-confirming.

Roadmap

Write-capable tools are a deliberate v2, shaped around the platform's approval workflows rather than generic read-write access.

Integration questions

Can my agent actually change records?

No. Every MCP v1 tool is read-only. A connected tool can submit, but nothing it submits is trusted until a different named person confirms it. Writes land Pending and the submitting identity is blocked from self-confirming.

Does MCP access require a new credential?

No. The MCP server is a thin, standards-based front door onto the platform's existing access boundary. It reuses the same Personal Access Token a Founder generates from Settings. No OAuth flow, no new credential type.

Is MCP access included in the seat price?

Yes. MCP access is a read path onto data your seats already pay for, so it is included in every seat at no extra charge.

Are write tools planned?

Yes, in v2, and they are deliberately shaped around the platform's approval workflows rather than generic read-write access. Until then, writes are PAT-controlled inside the app.

See all twenty-nine questions

Connect the tools your team already runs.

The first conversation covers which tools are in use today and what your agents would need to read.