MCP server overview

The Auxilian MCP server lets AI assistants read and write Auxilian projects as the signed-in user. It runs the same operations as the web app, so permissions, limits, validation, and the activity log behave identically on both surfaces.

Endpoint

Property	Value
URL	`https://mcp.auxilian.ai/mcp`
Transport	Streamable HTTP, stateless, JSON responses (no SSE stream, no session id)
Authorization	OAuth 2.1 bearer token. See Authorization.
Server name	`auxilian`

Tools

Tool	Scope	Kind	Purpose
`list_projects`	`mcp:read`	Read	Projects you can access and your workspaces
`list_tables`	`mcp:read`	Read	Every table in a project with its columns and foreign keys
`describe_table`	`mcp:read`	Read	One table’s columns and foreign keys
`list_rows`	`mcp:read`	Read	Rows, with filters, sorting, and paging
`create_project`	`mcp:write`	Write	A new project in a workspace
`create_table`	`mcp:write`	Write	A new table, optionally with foreign keys
`add_column`	`mcp:write`	Write	A new column on a table
`insert_rows`	`mcp:write`	Write	Up to 100 rows
`update_rows`	`mcp:write`	Write	Change rows that match filters
`delete_rows`	`mcp:write`	Destructive	Delete rows that match filters
`drop_column`	`mcp:write`	Destructive	Remove a column and its data
`drop_table`	`mcp:write`	Destructive	Remove a table and its rows

Each tool carries MCP annotations: read tools set readOnlyHint: true, destructive tools set destructiveHint: true, and every tool sets openWorldHint: false. Clients use these to decide when to ask you before running a tool. Operations that only exist in the web app: deleting projects, sharing projects, managing workspace members and invitations, renaming workspaces, exporting CSV, viewing the activity log, and deleting your account.

Server instructions

On initialization, the server tells the assistant:

Auxilian gives you Postgres databases ("projects") owned by the user. Call
list_projects first, then list_tables/describe_table before touching rows.
Every change is attributed to the user and visible in the project Activity
log. Prefer small, reversible steps; drop_* and delete_rows cannot be undone.

Identity and permissions

Every tool call runs as the user who approved the connection. The server applies that user’s current workspace roles and project permissions on every call, so access changes take effect immediately. See Permissions. A project you can’t access and a project that doesn’t exist return the same error, ACCESS_DENIED with the message Access denied, so ids can’t be probed.

Rate limits

Budget	Limit	Applies to
Calls	300 per minute per user	Every tool call
Writes	60 per minute per user	Write and destructive tools

The write budget is shared with the web app. When a budget runs out, the call fails with RATE_LIMITED. Wait a minute and retry. Insert rows in batches of up to 100 to stay within the write budget.

Typical call sequence

Next steps

Responses and errors explains the result format.
Filters explains row selection for list_rows, update_rows, and delete_rows.

Overview

Read tools

Write tools

Destructive tools

MCP server overview

Endpoint

Tools

Server instructions

Identity and permissions

Rate limits

Typical call sequence

Next steps

​Endpoint

​Tools

​Server instructions

​Identity and permissions

​Rate limits

​Typical call sequence

​Next steps

Endpoint

Tools

Server instructions

Identity and permissions

Rate limits

Typical call sequence

Next steps