Skip to developer setup
Open the app
A QUIETER SPACE TOGETHER

Your people.
Your keys.
Your space.

Good conversations. Carefully shared secrets. A lightweight home for your team—and the agents that help you build.

Open the app Connect an agent
Encrypted live chats & vaults · Local MCP sandbox
A LITTLE CLOSERUI PREVIEW
☀
The weekend peopleGood company. No noise.
TODAY
Maya

A little coffee, a little sunshine?

10:42

You had me at coffee ☕

10:43
Alex

And absolutely no work talk. 🌿

10:44
Write a little something…
Payments APIProduction vault
Rotate in 4d
•••• •••• •••• •••• Copy
Unlock first. Share with care.
Your next teammate is an agent.MCP ready. Access on your terms.
BUILT TO KEEP THINGS LIGHT
Less clutter
Device-side encryption
Open protocol
Your circle, your choice
JUST THE THINGS THAT MATTER

A place for the everyday.
And the things you keep close.

Thoughtful essentials, with room to breathe.

01 / CONVERSATIONS

Your people, a little closer.

One-to-one catch-ups and group conversations. Email accounts, a familiar interface, and encrypted messaging for live accounts.

Find your people
02 / SECRETS

Keys with a little context.

API names, stored dates and rotation reminders. Unlock to copy, then share an entire vault or just the key someone needs.

Explore the vault
03 / AGENTS

A thoughtful extra pair of hands.

Give a tool-calling agent a focused job. MCP tools start read-only, with separate permissions for writing, revealing and sharing.

Meet the tools
MADE FOR PEOPLE WHO BUILD

Your app.
Your agent.
A shared language.

Connect an MCP-capable host to ChatBoard’s local server. Discover the tools, pick the permissions, and let an agent help with the small stuff.

AVAILABLE NOW: LOCAL SANDBOX · STDIO
01

Prepare your local checkout.

Use Node.js 22 or later. From the ChatBoard project directory, install dependencies.

npm install

The MCP server runs independently; the web app does not need to be running.

02

Add it to your MCP host.

Copy the configuration into your host’s MCP server settings. Replace both C:/path/to/ChatBoard paths with your absolute project path. macOS and Linux use paths such as /Users/you/ChatBoard.

Launch with node, as shown. Use the direct command so stdout stays reserved for MCP.

03

Start with a small request.

Restart or reconnect your host, then ask: Check which sample API keys need rotation. The agent discovers IDs with list_vaults, then calls list_secrets.

No real credentials. No database setup.

mcp-config.jsonJSON
{
  "mcpServers": {
    "secrets-chat-demo": {
      "command": "node",
      "args": [
        "C:/path/to/ChatBoard/node_modules/tsx/dist/cli.mjs",
        "C:/path/to/ChatBoard/mcp/index.ts"
      ],
      "env": {
        "CHATBOARD_MCP_MODE": "demo",
        "CHATBOARD_MCP_PERMISSIONS": "chat:read,vault:read"
      }
    }
  }
}
Read-only by default. Permissions belong to the host.
A LITTLE ACCESS GOES A LONG WAY

Give each agent a clear role.

Add only the scopes you need to CHATBOARD_MCP_PERMISSIONS. Permissions are fixed at startup; tool calls cannot expand them.

chat:readDEFAULT

Read direct and group chats.

list_chats · read_chat
vault:readDEFAULT

Names, dates and rotation warnings. Keys redacted.

list_vaults · list_secrets
chat:writeOPT-IN

Create sample chats and send encrypted messages.

create_chat · send_message
vault:writeOPT-IN

Store fake keys. Updates need the current revision.

create_vault · save_secret
secret:revealOPT-IN

Explicitly return one key value to the agent.

reveal_secret
secret:shareOPT-IN

Share a vault or one key with a sample teammate.

share_secret

Every connection also gets session_status, session_lock and audit_log. Locking requires a manual process restart to reconnect. The audit retains the last 100 tool outcomes in memory, without keys or arguments.

BUILDING YOUR OWN AGENT?

Bring an MCP client to your tool calls.

Your application launches the stdio server, initializes an MCP client, and maps tools/list names, descriptions and JSON schemas into the model’s function definitions. Route the model’s chosen function calls to tools/call, then return the result to the model. Tool calling alone does not provide an MCP connection.

YOUR MODELMCP CLIENTCHATBOARD
Full setup & tool reference Machine-readable agent guide Official MCP SDK docs
GOOD TO KNOW

A few answers.
No fine print.

Clear boundaries make better tools.

Is this connected to my real chats and keys?

The current MCP server uses its own encrypted, in-memory sample data. It is separate from the app and your account. Restarting clears edits and creates new IDs. Live account access is not available yet.

Can an agent see API keys?

Key lists return names, dates and rotation warnings—not key values or notes. To return a key, the host must explicitly enable secret:reveal and call reveal_secret. Anything revealed enters the host and model context. Use fake credentials only; stored sandbox keys must start with demo_.

How do sending and sharing work?

Enable chat:write to send messages and secret:share to share sample keys. Your MCP host must ask for human approval before sending or sharing; tool annotations are hints, not an approval system. Sharing a vault includes future keys; sharing one key does not expose sibling keys. There is no expiry or revocation yet.

Can I use a remote MCP URL on Vercel?

This version uses local stdio and has no remote MCP URL. A hosted version needs Streamable HTTP, OAuth authorization, scoped identities, location checks, revocation and production verification. The live database gateway guard remains pending.

What does encryption protect?

Live chats and vaults encrypt content on the device. Browser chat samples are unencrypted; MCP samples use signed encryption. The current encryption is unaudited and has no forward secrecy. An authorized agent can retain disclosed plaintext, and metadata remains visible to the backend. An independent review and live-account testing are required before sensitive production use.

LESS NOISE. MORE CONNECTION.

A little space
for what matters.

Make yourself at home Or bring an agent

Start a conversation. Build thoughtfully.