AI assistants

Your calls, inside your AI assistant.

Connect Claude, Cursor or your own tools to ActiveLens and ask about your calls, meetings, tasks and documents. Read-only, with your own permissions.

https://app.activelens.ai/api/mcp

Live today. Open ActiveLens

Read-only

An assistant can search and read. It never changes anything in ActiveLens.

Your permissions

An assistant sees exactly what its person can see in ActiveLens, nothing more.

Every call logged

Every tool call is recorded in your workspace's audit log.

Try asking

“Summarize my calls with Northgate this month”

“What did Emily Carter ask about on Tuesday's call?”

“Which of my follow-up tasks are overdue?”

“What did customers say about pricing in October?”

Who can connect

Everyone in an ActiveLens workspace on the Basic plan or higher. See plans
A workspace admin can turn it off for everyone in Settings › Security, under “Let people connect AI assistants (MCP)”.
External collaborators can't connect.

Connect

For claude.ai and Claude Desktop. No key needed: you sign in to ActiveLens instead.

1In Claude, open Settings › Connectors and choose Add custom connector.
2Paste https://app.activelens.ai/api/mcp.
3Sign in to ActiveLens and choose Allow.

1In ActiveLens, go to Settings › AI assistants › Personal API keys and choose Create key. Copy it now: it's shown only once.
2Run this, with your key in place of YOUR_API_KEY:

claude mcp add --transport http activelens https://app.activelens.ai/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

Any assistant that supports remote MCP servers connects the same way: the address above, with the header Authorization: Bearer YOUR_API_KEY.

1In ActiveLens, go to Settings › AI assistants › Personal API keys and choose Create key. Copy it now: it's shown only once.
2In Cursor, add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project:

.cursor/mcp.json

{
  "mcpServers": {
    "activelens": {
      "url": "https://app.activelens.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Rather not keep the key in the file? Cursor can read it from an environment variable: "Bearer ${env:ACTIVELENS_API_KEY}".

The server speaks JSON-RPC 2.0 over HTTP POST. It's stateless: no sessions, plain JSON replies. Supported protocol versions: 2025-06-18, 2025-03-26 and 2024-11-05.

1In ActiveLens, go to Settings › AI assistants › Personal API keys and choose Create key. Copy it now: it's shown only once.
2List the tools, for example:

curl https://app.activelens.ai/api/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

What an assistant can do

Six read-only tools. Read-only today: no tool changes anything in ActiveLens.

search_calls

Find recorded calls and meetings by words said or summarized, a date range, or a person.

get_call

One call: title, date, length, participants, AI summary, notes, chapters, follow-up tasks, and a link to open it in ActiveLens.

get_call_transcript

The call's speaker-labeled transcript. Long calls come in pieces.

list_tasks

Follow-up tasks the person can see: open ones by default; filter by status, “assigned to me”, or due by a date.

ask_activelens

Ask ActiveLens's own AI a question across all calls (trends, counts, “what did customers say about pricing this month?”), answered with numbered sources. A long question returns an id to collect the answer with.

search_knowledge

Search the workspace's uploaded reference documents: product sheets, price lists, policies, manuals.

Managing access

Everything lives in ActiveLens under Settings › AI assistants.

Personal API keysShown once when created. They expire after 30, 90 (the default) or 365 days. Up to 10 active keys per person, and you can revoke any of them at any time.

Connected appsAssistants you connected by signing in, such as Claude, are listed with a Disconnect button.

AdminsAdmins see and revoke every connection and key in the workspace, and can turn the feature off.

Stored safelyKeys and tokens are stored only as hashes, and every tool call is recorded in the workspace's audit log.

For MCP client developers

Discovery. Protected-resource metadata (RFC 9728) at https://app.activelens.ai/.well-known/oauth-protected-resource and authorization-server metadata (RFC 8414) at https://app.activelens.ai/.well-known/oauth-authorization-server. A 401 from the server names the metadata in WWW-Authenticate.
OAuth. Dynamic client registration (RFC 7591) at /api/oauth/register; authorization code with PKCE (S256); public clients, with no client secret; scope read; revocation at /api/oauth/revoke.
Tokens. Access tokens last 1 hour. Refresh tokens last 30 days and are rotated on use.
Rate limits. 60 tool calls per minute per connection, and 120 per person across all their connections.
Protocol. JSON-RPC 2.0 over HTTP POST, stateless. Protocol versions 2025-06-18, 2025-03-26 and 2024-11-05.

Ready to connect?

Create a key or connect Claude in Settings › AI assistants.

Open ActiveLens