---
title: "MCP Server"
description: "Remote MCP endpoint for AI agent integration."
canonical: "https://pgbeam.com/docs/api/mcp"
last-updated: "2026-09-14T19:37:21.000Z"
---

# MCP Server

> Remote MCP endpoint for AI agent integration.

URL: https://pgbeam.com/docs/api/mcp

`POST /v1/mcp` is a remote Model Context Protocol server using the Streamable HTTP transport. It lets AI assistants manage PgBeam resources (projects, databases, policies, agent credentials) through three meta-tools rather than one tool per endpoint.

See the MCP command docs for full setup instructions covering both the CLI (stdio) and remote (HTTP) transports.

This is the **management** MCP — it administers your account. To give an agent
**query access to a database**, use the hosted agent-database
MCP, a separate endpoint with `briefing`, `query`, `validate_sql`,
`list_tables`, `describe_table`, `explain`, `schema_catalog`, and
`my_permissions` tools enforced by your policies, plus `search_docs` and
`read_doc`.

## Quick start

## Protocol

Property

Value

Transport

Streamable HTTP (MCP spec 2025-03-26)

Wire format

JSON-RPC 2.0

Auth

`Authorization: Bearer <token>`

Methods

`initialize`, `notifications/initialized`, `tools/list`, `tools/call`, `ping`

## Authentication

The MCP endpoint uses the same authentication as the REST API. Pass a bearer token or API key in the `Authorization` header. See Authentication.

## Tools

`tools/list` returns three meta-tools that wrap the whole API. This keeps the agent's context small — it discovers operations on demand instead of loading a schema for every endpoint up front.

Tool

Purpose

`search_endpoints`

Find operations by intent (`query`, `limit`). Returns `operation_id`, `method`, `path`, `tag`.

`describe_endpoint`

Full schema for one operation (`operation_id`): parameters and request body.

`call_endpoint`

Invoke an operation: `operation_id`, plus `path_params`, `query_params`, and `body` as needed.

The operation ids and shapes mirror the OpenAPI spec. A typical flow is `search_endpoints` → `describe_endpoint` → `call_endpoint`.