gifos-mcp
Related Servers
Alternatives to gifos-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceLets Grok Bot or any MCP client schedule a GifOS broadcast with complete invite details (link, start and end times, visit link, ready-to-send text), run the host's booth to go live, play a prerecorded video and end the stream, and seat a note-taking bot that transcribes what is said on stage. It runs entirely on the user's own machine, broadcasting over GifOS's peer-to-peer fan-out with no account, API key, or hosted endpoint.36-
- AlicenseAqualityCmaintenanceEnables AI agents to join online meetings as a silent guest, record audio locally, generate transcripts with timestamps via faster-whisper, and manage recordings through MCP tools.6MIT
- AlicenseBqualityCmaintenanceEnables local MCP clients to interact with xAI Grok through OAuth PKCE, supporting chat, X search, image/video generation, TTS, and transcription.96 npm3MIT
- FlicenseNot gradedqualityDmaintenanceAutomates Grok web interface to provide chat, web search, and conversation management via MCP, supporting multiple accounts and local/remote deployment.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents like ChatGPT and Claude to securely access a Grok Bot workstation's folder-scoped files, shell, and Git tools over HTTPS+OAuth or local stdio, and to orchestrate specialized Grok Bot agents via a message bridge.1MIT
- AlicenseNot gradedqualityBmaintenanceLets an MCP client read your screen-and-voice recordings — timed transcripts and the frames that matter — so it can write up tasks with screenshots and file them on GitHub Issues, Linear, Jira, Trello, Asana or Azure DevOps. Everything is transcribed locally, so the agent does the AI work on your own subscription.MIT
TDQS
Scored across 10 tools
Each tool targets a distinct action, and the descriptions actively disambiguate the subtle create_meeting vs start_meeting vs join_meeting distinction (create only makes a link, start joins your own, join handles someone else's). mute/unmute and share_content/get_transcript are obviously separable. No two tools appear to do the same thing.
The set is dominated by a clean snake_case verb_noun pattern (list_meetings, create_meeting, start_meeting, join_meeting, share_content, get_transcript, end_meeting). The single-word tools mute, unmute, and status are minor deviations from that pattern but remain clear and readable.
Ten tools is well within the ideal range and each one covers a real stage of the meeting-bot lifecycle. Nothing feels padded or redundant; the surface is tightly scoped to the server's purpose.
The lifecycle is largely covered: create, start, join, list, mute/unmute, share, retrieve transcript, end, and status. Minor gaps remain (e.g. no tool to fetch or delete a single meeting, and no way to remove/inspect an ended meeting beyond the transcript), but core workflows are usable end to end.