What dependencies are required to run the server?
Requires Python 3.10+ and access to a PostgreSQL database. Docker is recommended for easy deployment; `uv` is used for local dependency management.
@Alexander-Nestor-Bergmann
基本情報
A template for how to build an MCP server
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"agents-mcp-demo": {
"command": "docker",
"args": [
"build",
"-t",
"sql-mcp-demo-server",
"--build-arg",
"PORT=${DB_PORT:-8051}",
"."
]
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
A Template MCP Server is an example implementation of a Model Context Protocol (MCP) server that demonstrates how to connect AI agents and services (like Claude) to external data sources. It uses a PostgreSQL database backend to manage user data and exposes simple tools for user operations, serving as a reference for building MCP servers.
Configure environment variables (especially DB_URL) in a .env file, then run the server using Docker or local Python. Connect an MCP client using either SSE (via Docker) or stdio transport (for local development). Example client configuration for SSE: set transport to sse and url to http://localhost:8051/sse.
DB_URL, DB_HOST, DB_PORT).Requires Python 3.10+ and access to a PostgreSQL database. Docker is recommended for easy deployment; `uv` is used for local dependency management.
Set the `DB_URL` environment variable to a PostgreSQL connection string using an asyncpg compatible prefix (e.g., `postgresql+asyncpg://user:pass@host:5432/dbname`). Additional optional variables like `DB_HOST`, `DB_PORT`, and `MCP_SIGNING_KEY` can be set in a `.env` file.
The server supports both SSE (Server-Sent Events) transport, typically used when running via Docker, and stdio transport for local development. The client configuration must specify the transport type and appropriate connection details.
No. The tools are simplified examples and the server is designed as a template to illustrate MCP server construction. The README explicitly states it is not for production use.
Data lives in a PostgreSQL database configured via the `DB_URL` environment variable. The server itself does not store data; it acts as a gateway to the external database.

Open-source Next.js + Supabase CMS with a per-site MCP server: scaffold a site, then create pages, posts, navigation, media and SEO from Claude, Cursor or any MCP client. Streamable HTTP with a bearer token you mint in y

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.


SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

Agent Trust — open profile + reference implementation for proving what an autonomous AI agent is authorized to do: identity, delegation with attenuation, proof-of-possession, attestations, tamper-evident provenance. Buil
コメント