Find the right link
Look up domains, recent links, or one exact link without switching back to the dashboard.
- List workspace domains and recent links
- Find a link by URL, domain, or short code
- Check custom slug availability
AI tool integrations
Connect AI tools to your Nimriz workspace.
Use the Nimriz Model Context Protocol (MCP) server to give compatible assistants and coding tools permissioned access to link operations, analytics summaries, and delivery health.
OAuth where supportedWorkspace-scoped accessAudited link creation
Remote MCP connection
Client to workspace, with Nimriz enforcing every boundary
Your AI tool
Claude
ChatGPT
Codex CLI
CursorNimriz workspace
N
Permissioned tools
Authorized for one workspace
Links
Find and create
Analytics
Summary results
Destinations
Delivery health
Webhooks
Delivery health
1Authenticate
2Authorize
3Run a workspace tool
Workspace capabilities
Work with links, analytics, and delivery health.
Use focused tools to find and create links, review performance, and check connected systems from the same conversation.
See the complete tool referenceCreate branded links
Turn an approved brief into one link or a bounded batch while Nimriz applies the same rules as the dashboard.
- Create one short link
- Create a bounded batch with per-item results
- Honor reserved slugs, limits, and plan entitlements
Bring analytics into the conversation
Ask for performance context when preparing a report, reviewing a campaign, or investigating a result.
- Summarize total and human click counts
- Review a daily click series
- Compare top referrer, location, device, and target-host values
Inspect delivery health
See configured destinations and webhooks, then review recent delivery status without exposing connection secrets.
- List destinations and subscribed webhooks
- Review delivered, retrying, and failed counts
- Check delivery status without provider payloads or error details
Workflow examples
Move from a question to a verified workspace result.
Build campaign links, review performance, and investigate delivery health without leaving your AI tool.
Campaign production
01Go from brief to branded links
“Prepare links for the approved campaign destinations.”
- 1Find the correct workspace domain
- 2Check the requested slugs
- 3Create the links and return per-item results
Live links are created only after Nimriz validates permissions, domain rules, and plan limits.
Performance review
02Answer a campaign question with workspace context
“How did this link perform, and where did its human traffic come from?”
- 1Find the existing link
- 2Read its aggregate analytics summary
- 3Compare the requested breakdown values
The assistant can work with summarized results without receiving raw click records, IP addresses, or full user agents.
Operations review
03Investigate delivery health in context
“Check whether our destination and webhook deliveries are healthy.”
- 1List configured connections
- 2Read recent status counts
- 3Review the latest safe delivery status
Signing secrets, destination credentials, provider payloads, and provider error details stay out of the response.
Connection choice
Start with OAuth when your client supports it.
Both paths are workspace-scoped. The difference is how the client authenticates and how you manage that connection.
Recommended where supported
Nimriz OAuth
Approve access through Nimriz sign-in
Choose a workspace and approve the scopes the client requests. The grant is bound to the MCP resource and can be revoked from Nimriz.
- No API key to paste into the client
- Explicit workspace and scope approval
- Disconnect by revoking the OAuth grant
OAuth-capable clients
Claude, ChatGPT, Claude Code, Codex CLI
Workspace API key
Connect clients that use key-based authentication
Use a key created for the workspace when a compatible client cannot use Nimriz OAuth. The key carries the scopes assigned to it and can be revoked independently.
- Works with supported header-based clients
- Tied to one Nimriz workspace
- Revoke and replace a key if it is exposed
Compatible clients
9 listed in the directory below
Key safety: if a client stores a workspace API key inside a connector URL, treat the entire URL as a secret. Do not share it or post screenshots of it. Revoke the key if the URL is exposed.
Trust boundaries
The AI client proposes. Nimriz authorizes and enforces.
MCP is another way to use Nimriz features. It does not bypass workspace rules, reveal connection credentials, or create a separate permission model.
One workspace identity
The connected workspace comes from the approved OAuth grant or API key. A tool cannot choose a different workspace in its request.
Server-enforced permissions
Nimriz checks scopes, ownership, plan entitlements, and tenant boundaries for every call, regardless of the client interface.
Privacy-shaped analytics
Analytics responses contain aggregate counts. They do not include raw click rows, IP addresses, or full user-agent strings.
Visible write activity
Created links are live, count toward the workspace link limit, and appear in the audit log with MCP as their source.
Compatible client
Presents an approved credential
Nimriz authorization
Checks scopes, ownership, and limits
Bounded result
Returns only the allowed fields
Client directory
Find the connection path for your AI tool.
This directory reflects the AI tool connections available in the Nimriz dashboard. Use the setup guide for current configuration steps.
Claude
Use Nimriz sign-in with a custom connector.
Nimriz OAuthWorkspace API key
ChatGPT
Use OAuth with a custom MCP connector.
Nimriz OAuth
Claude Code
Use a public OAuth client from the CLI.
Nimriz OAuthWorkspace API key
Codex CLI
Use a public OAuth client from the CLI.
Nimriz OAuthWorkspace API key
Cursor
Use mcp.json with an Authorization header.
Workspace API key
Gemini CLI
Use settings.json with an Authorization header.
Workspace API key
Kiro
Use mcp.json with an Authorization header.
Workspace API key
Replit
Add a server URL and Authorization header.
Workspace API key
MCP Inspector
Debug the server's tools with a header key.
Workspace API key
Other MCP clients
Use OAuth if offered, otherwise send a header key.
Workspace API key
Decision guide
Questions before you connect
Choose the client and authentication path first. The setup guide covers the exact configuration after that decision.
Is MCP the right connection for my AI tool?
Use the Nimriz MCP server when your assistant, coding tool, or agent environment supports remote MCP over Streamable HTTP. Use the Nimriz API instead when your own backend should control requests directly.
Should I choose OAuth or a workspace API key?
Choose OAuth when the client presents Nimriz sign-in. It lets you select a workspace, approve requested scopes, and revoke the grant from Nimriz. Use a workspace API key for a compatible client that requires key-based authentication.
What can a connected AI tool change?
MCP can create one short link or a bounded batch of links. Existing link updates and deletes, webhook management, destination management, and API key management remain outside the MCP tool set.
Can one connection reach multiple workspaces?
No. Each OAuth grant or workspace API key is tied to one workspace. Every request is authorized against that workspace before a tool runs.
Does the AI tool receive raw analytics or integration secrets?
No. Analytics tools return summarized counts, and health tools return delivery status without sensitive provider details. Raw click records, IP addresses, full user agents, signing secrets, destination credentials, and provider error payloads are excluded.
Where do I find setup instructions?
Use the MCP setup guide for the current client-by-client steps. The dashboard AI tools area also provides the applicable OAuth guidance and API-key fallback options for your workspace.
Connect your first AI tool
Put Nimriz workspace context inside the AI tool where work already happens.
Create a workspace, choose a compatible client, and follow the maintained MCP guide for its connection steps.