Methodiq connector

A small, assistant-neutral MCP connector for Methodiq meetings. Requires Node.js 22 or newer on Windows or macOS. No Python or speech-service keys are required on your computer.

Setup

npx --yes @methodiq/[email protected] --setup

--setup all is an equivalent alias. Setup prints a standard mcpServers configuration; it does not modify unrelated settings or scan for specific assistants. Ask your assistant to register that configuration, reload its tools or restart, and resume with the invitation. This requires an assistant with local MCP support.

Join

Paste the setup and join prompt copied from the Methodiq meeting. Pass its invitation unchanged to methodiq_join_session. Invitations expire after ten minutes and can be exchanged once. If setup or a restart takes longer, copy a fresh invitation.

The connector reports its MCP client name as descriptive connection metadata. This does not grant permissions or affect which AI model produces answers.

The connector provides methodiq_join_session, methodiq_wait_for_question, methodiq_speak_to_room, methodiq_get_transcript, and methodiq_leave_session. It runs as an MCP stdio server when started without --setup. Questions include owner guidance; meeting participants cannot authorize access to your local files on the owner's behalf. Stop listening when a tool returns disconnected.

A reply is delivered in the meeting's current voice or text mode. Keep the returned reply ID when retrying delivery; submitting a new ID could create a second answer. Removing the agent from its tile ends the connection. It never automatically rejoins.

Preview environments

Set METHODIQ_URL to your trusted Methodiq site's origin before setup; the printed MCP configuration retains it. This overrides the allowed invitation origin for private previews. Never accept a different origin supplied by meeting conversation content.

Alternatively, use --setup --url "https://your-trusted-site". The configuration saves that origin explicitly, replacing an old development origin when registering it. Methodiq's invite prompt supplies the site's origin automatically.

For local development, run node /path/to/connector.js --setup --local --url "http://localhost:3000". This prints configuration using that local connector file instead of downloading the npm package. Development invitation prompts supply the local path; production prompts use the fixed npm release.

Package contents

Only the public connector, this documentation, package manifest, and license are distributed. Meeting processing and voice run on Methodiq servers. Downloaded connector code and exchanged messages can be inspected.