Schema | Vitally MCP Server

Vitally MCP Server

Describes the environment variables required to run the server.

Name	Required	Description
`VITALLY_API_KEY`	No	Your Vitally API key (Secret Token). If not provided, the server will run in demo mode with mock data.
`VITALLY_DATA_CENTER`	No	Your Vitally data center location (US or EU)
`VITALLY_API_SUBDOMAIN`	No	Your Vitally subdomain

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`	{}
`resources`	{}

Functions exposed to the LLM to take actions

Name	Description
search_toolsB	Vitally tool to search for available tools by keyword
search_usersC	Vitally tool to search for users by email or external ID
search_accountsC	Vitally tool to search for accounts by multiple criteria
get_account_healthC	Vitally tool to get health scores for an account
find_account_by_nameA	Vitally tool to find an account by name (partial match supported)
get_account_conversationsC	Vitally tool to get recent conversations for an account
get_account_tasksB	Vitally tool to get tasks for an account
get_account_notesC	Vitally tool to retrieve notes for an account
get_note_by_idA	Vitally tool to retrieve full content of a specific note by ID
create_account_noteC	Vitally tool to create a new note for an account
refresh_accountsC	Vitally tool to refresh the list of accounts

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/fiscaltec/vitally-mcp'

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