Skip to content
NextCue
The workspacePrivate deploymentSupport
Talk to us
The workspacePrivate deploymentSupportContact us

NextCue MCP setup

Your Agent.
Your connection.

Ask your Agent to connect NextCue. It handles the preparation, downloads and configuration, and asks you only for what it needs.

What you need

An existing NextCue installation, your own account and an Agent that can configure your local Codex client. The Agent prepares the required runtime on macOS, Windows or Linux.

Your other MCP connections and existing NextCue tool restrictions are preserved. If your installation uses a private network or VPN, make sure your device can reach it.

1. Give this request to your Agent

Copy this message into your Agent:

Install NextCue MCP from https://github.com/samhu70/nextcue-mcp. Prepare the environment and configure my local client automatically. Ask me for my NextCue address if it is missing. Use protected local input for the personal token; do not ask me to paste it into chat. Preserve my other MCP settings and verify the connection afterwards.

The Agent follows the installation instructions, verifies the download and runs setup in the background.

2. Provide only missing information

The Agent may ask for your NextCue installation’s HTTPS address. An existing private token can be reused for an existing connection to the same installation.

If a new token is needed, create one in your NextCue account and enter it through the protected local input prompt arranged by the Agent. You do not need to type installation commands or edit configuration files.

Keep tokens out of chat messages, email and public issues. A protected input handoff depends on your Agent’s capabilities; the Agent should explain that one handoff if needed.

Where do I find my address and token?

Open your own NextCue installation and sign in. Its address comes from your administrator. Open Account → Manage MCP connection tokens (/Account/McpTokens) and create a token for your client.

This public website does not issue tokens for your private workspace. Google browser sign-in does not automatically grant MCP access.

3. Let the Agent check the connection

The Agent completes setup, then checks get_context for your expected account and workspaces and uses search_tasks for a read-only access check. If your client needs a reload, the Agent will tell you.

Configuration and verified access are reported separately. Your Agent should not create test tasks or change your business data just to check the connection.

When your token expires

Personal MCP tokens currently expire after 30 days. Ask your Agent to renew the connection. It can reuse the known address, request a replacement token through protected local input and update the connection.

Explicitly signing out of NextCue invalidates existing MCP tokens. Closing your browser alone does not. A token from one installation cannot connect to another.

If you need help

Ask your Agent to check the installation address, private network or VPN, trusted HTTPS certificate and token expiry. Do not disable certificate verification or loosen credential-file permissions to force a connection.

For product support, contact nextcue@fivexing.com.au. Share non-sensitive error details and keep tokens, passwords, private keys and workspace data private.

For Agents: downloads, setup protocol and manual fallback

Connection kit

Download connection kit (ZIP)

Releases and checksums · Agent installation guide

The Agent detects or provisions Python 3.11+ and invokes the installer in noninteractive mode:

python install.py --agent

JSON status input_required names missing information. The Agent supplies the URL and a private token-file path, then resumes. The token itself is never passed as a command argument.

What setup changes

Setup installs a permanent helper, updates only the nextcue connection and backs up an existing configuration as config.toml.nextcue-backup-…. It preserves other servers and NextCue tool permissions. Unsupported inline layouts, symbolic-link targets and Windows junction targets are rejected before configuration changes.

Tokens are stored outside config.toml in a private local file. macOS/Linux use file permissions 600; Windows limits access to the current user and SYSTEM. Programs running as your operating-system account can read the file; this is not a system keychain. Setup stores one NextCue token per operating-system account.

Manual fallback

The existing interactive installer remains available through python install.py. Other MCP clients can use their own private Bearer-token setting with Streamable HTTP. This kit does not provide OAuth login.

Back to support

NextCue

Your next step, in one place.

PrivacyTermsSupportMCP setupContact
© 2026 NextCueA FiveXing project