boundry.
Open dashboardDashboard

Connect an agent, not a password.

Boundry runs a hosted Model Context Protocol server in Sydney. A compatible client discovers OAuth automatically, and you approve one project — the agent never receives your password, Clerk session, or a copied API key.

https://api.boundry.dev/mcp
Read the setup guide
  • Streamable HTTP · OAuth 2.0
  • Sydney · ap-southeast-2
  • Control origin Australia · only region today
Approve BoundryOAuth request
Client
MCP agent
Organisation
Acme Pty Ltd
Project
acme-production · Sydney
Scope
This project only

Boundry never receives your password, Clerk session, or a copied API key.

Three approvals, then it can work.

Connecting an agent to Boundry is a human-approved handoff, not a shared secret. Every step below comes from the public setup guide.

Add the endpoint.

Give your MCP client the remote server address below. It discovers Boundry’s OAuth and authorization-server metadata, registers its callback, and opens the approval page automatically.

Authorise.

Sign in, then review the client name, callback host, project, region and requested scopes before you approve. Boundry and Clerk keep your credentials — the agent never receives them.

Pick the project.

Choose one Sydney project, or create an organisation and project during the handoff if you don’t have one yet. The grant is limited to that project and you can revoke it at any time.

Add it to your client.

Boundry’s remote server uses OAuth 2.0 with dynamic client registration, so a compatible client only needs the URL below.

Settings → Connectors → Add custom connector
{
  "name": "Boundry",
  "url": "https://api.boundry.dev/mcp"
}

Ten tools, scoped to one project.

Once a project is authorised, the agent can call these tools. Read tools never change data. Write and destructive tools are annotated for the client and always act inside the approved project.

Read the full setup guide

Read

get_guide

Discover the integration workflow, select a published SDK and load the right implementation guide.

get_project

Inspect the authorized project and its regional boundary.

list_regions

Separate live regions from markets where Boundry is measuring demand.

list_domains

List sending and receiving domains and their status.

list_messages

List outbound or inbound messages in the project.

get_message

Inspect one outbound or inbound message.

Write

request_region

Record an approved region request. This never promises a launch or reserves capacity.

create_domain

Create a project domain and return the DNS records to publish.

verify_domain

Check published DNS and refresh verification status.

Destructive

send_email

Send from a verified domain. An idempotency key is always required.

Connect your first agent.

Point any Streamable HTTP MCP client at the endpoint below, sign in, and approve one Sydney project.

https://api.boundry.dev/mcp
Read the setup guide