Schema | EarSay MCP

EarSay MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
voice_startA	Start the EarSay transcription server if not already running. Call this once before using any other voice_* tools. If the server is already running, this is a no-op.
voice_stopA	Stop the EarSay transcription server and release the microphone.
voice_pauseA	Pause transcription. The microphone is released but the server stays alive. Call voice_resume to start listening again.
voice_resumeA	Resume transcription after a pause. The microphone is re-opened.
voice_get_textA	Get all transcribed text since the server started. Returns the complete transcript buffer.
voice_get_newA	Get text transcribed since the last checkpoint. Returns the new text and its potential checkpoint index. Use voice_set_checkpoint to mark what you've already read.
voice_set_checkpointA	Set a checkpoint at the given character position. This marks all text up to char_position as 'read'. Subsequent calls to voice_get_new will only return text after this position. Args: char_position: Character position in the transcript buffer (1-indexed). Must be after the last checkpoint and not exceed the total available text.
voice_statusA	Get the current status of the EarSay server. Returns status (listening/paused/stopped), uptime, character count, checkpoint count, and subscription count.

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/AlastorMordrek/earsay-mcp'

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