GimmeText

com.gimmetextPublished by gimmetext.comOfficial publisherv1.2.0Updated Oct 24, 2026

Turn any recording into text your AI can use — private speech-to-text over a remote MCP server.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

GimmeText is a remote MCP server that turns recordings into text an AI assistant can use, described as private speech-to-text.

What you can do
Convert recordings into text that the assistant can work with, according to the provider's description of private speech-to-text over a remote MCP server. No individual tools are listed in the supplied material, so the exact operations available are not documented here. The service is reached as a hosted remote endpoint rather than a local package.
When to use it
Consider it when you want an assistant to work with spoken content from recordings and prefer a hosted speech-to-text service over running transcription locally.
Requirements
A remote MCP connection to the provider's hosted endpoint over streamable HTTP, plus OAuth sign-in, which the manifest marks as required. No environment variables or headers are declared.
Before you install
Recordings are sent to a third-party hosted service for transcription, so consider whether the audio contains sensitive or confidential content. OAuth grants the server access tied to your account; review the scopes requested during sign-in. No tool list is published, so confirm what the server can do before relying on it.

Installation

In SourceWeft

  1. Open GimmeText in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.gimmetext%2Fgimmetext/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gimmetext": {
      "type": "http",
      "url": "https://gimmetext.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.2.0LatestOct 10, 2026
  2. v1.1.0Oct 10, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.