// use case — mcp

in production · being verified

Your AI assistant, working inside your workspace.

niiko is a remote MCP server with OAuth: no keys pasted in a file. You authorize from a screen that says who is asking, on which workspace, and exactly which actions — none pre-checked.

Built and running in production; we're verifying it client by client. If yours doesn't fit, tell us.

Create your workspace

// how it works

Step by step

01

Add niiko to your client

Point Claude — or any client that supports remote MCP servers — at niiko. It discovers the server and asks you to authorize.

no install, no key file
02

Read who is asking

The consent screen shows the client's name as it declared it, where it returns to, and the workspace you're granting access on.

the control is the screen
03

Tick the actions

Create leads, log calls, move deals, propose invoices, send broadcasts… Each is a checkbox, none checked by default. What you tick is what the token carries.

least privilege, by you
04

Work, and revoke when you want

The assistant acts with the same rules as a person with that role. Administration → Security lists every grant and revokes it in one click.

yours to take back

// what you need

Before you start

  • An MCP client that supports remote servers with OAuth (Claude does).
  • An owner or admin of the workspace to authorize — a member can't grant what they can't do.

// plans

Every plan, within its API caps: Free too. The actions available match what the plan's modules include.

Modules involvedPlatformMiiraCRMKiipu

See the plans →

Other use cases

What it does NOT do yet

Said plainly

  • The assistant only does what the catalog exposes as an action; it doesn't get free rein over your data.
  • A token is for one workspace: another workspace is another authorization.

// start

Connect your assistant

Create the workspace, open your MCP client and authorize. The first action takes a minute.

Create your workspace