Tembo MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
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.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_appsC | Get attributes for all apps |
| get_appC | Get the attributes of a single App |
| ask_temboC | Ask a question to Tembo Docs |
| get_instance_schemaB | Get the json-schema for an instance |
| get_all_instancesC | Get all Tembo instances in an organization |
| create_instanceC | Create a new Tembo instance |
| get_instanceC | Get an existing Tembo instance |
| delete_instanceC | Delete an existing Tembo instance |
| patch_instanceC | Update attributes on an existing Tembo instance |
| restore_instanceC | Restore a Tembo instance |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools target specific resources (instances, apps, docs) and actions (create, get, delete, patch, restore, ask), making it easy for an agent to select the correct one. For example, get_instance and get_all_instances are clearly differentiated by scope, and create_instance vs. patch_instance vs. restore_instance cover distinct lifecycle stages.
All tools follow a consistent verb_noun pattern using snake_case, with verbs like get, create, delete, patch, restore, and ask paired with specific nouns (instance, app, schema, tembo). The pattern is uniform across all 10 tools, making them predictable and easy to understand at a glance.
With 10 tools, the count is well-scoped for managing Tembo instances and related resources. Each tool earns its place by covering essential CRUD operations, lifecycle management, and auxiliary functions like schema retrieval and documentation queries, without being overly sparse or bloated.
The tool set provides complete coverage for the domain of managing Tembo instances and apps. It includes full CRUD operations for instances (create, get, patch, delete) and apps (get, get_all), plus lifecycle actions like restore and schema retrieval, with no obvious gaps that would hinder agent workflows.