mcpify
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCPIFY_AUTH | No | Authorization header value (e.g., 'Bearer <token>') applied to all API calls |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listPetsC | List all pets |
| createPetD | Create a pet |
| getPetB | Get a pet by ID |
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 3 tools
Each tool has a distinct purpose: create, get by ID, and list all pets. No ambiguity or overlap.
All tools follow a consistent camelCase verb_noun pattern: createPet, getPet, listPets.
Three tools is appropriate for a basic pet management scope, though slightly minimal.
Domain is pet management; missing update and delete operations are notable gaps for full lifecycle.