Schema | MCP API Engineering Lab

MCP API Engineering Lab

Describes the environment variables required to run the server.

Name	Required	Description	Default
`DATABASE_URL`	No	PostgreSQL connection string. If defined, the get_database_schema tool queries information_schema. If not, a sample schema is used.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
get_database_schemaA	Read a PostgreSQL schema from DATABASE_URL. Falls back to a local sample schema when no database is configured.
list_api_contractsA	List local OpenAPI YAML contracts available in the lab.
get_api_contractB	Read an OpenAPI contract from the local contracts folder.
create_api_contractB	Create a new minimal OpenAPI 3.1 contract in the local contracts folder.
update_api_contractB	Update the title or version of an existing local OpenAPI contract.
delete_api_contractA	Delete a local OpenAPI contract. The base template is protected.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/joseant1215/mcp-api-engineering-lab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server