Productive

Diskret connects to Productive’s official MCP server (https://mcp.productive.io/mcp). Productive lets an MCP client register itself, so you do not create an app or copy a client ID: you add the URL, and each user signs in to Productive once.

Time: about 5 minutes for the admin, then one sign-in per user. Who: a Diskret admin, and a Productive admin who can turn on AI features.

What Diskret can access

Productive’s MCP server covers projects and tasks, deals, companies and contacts, bookings and time off, time entries, invoices and expenses, people and teams, docs and comments, and reports. Much of that is personal data: client contacts, employees’ names, time entries, comments.

Scope	Why	Required
read	Look up projects, tasks, people, deals, time and reports	Yes
write	Create and change tasks, log time, add comments, create invoices	Only if users should make changes

Start with read only. You can add write later. Every response passes through Diskret’s field rules and pseudonymisation before it reaches the AI client, and write tools stay closed until an admin opens them.

Caution

Productive publishes the read and write scopes in its OAuth metadata but does not document which tools each scope allows. Check the tool list after the first sign-in (step 3) rather than relying on the scope alone.

Before you start

• Your Productive organization is on the Ultimate plan. The MCP server is not available on other plans.
• AI features are turned on in Productive.
• Each connection reaches one Productive organization. A user who belongs to several picks one when signing in.

1. Add the connector in Diskret

1. In Diskret, go to Connectors → New connector.
2. Type: MCP server. Name it (e.g. Productive) and set the URL to https://mcp.productive.io/mcp.
3. Under Authentication, choose Sign in with OAuth, and under Whose credential choose Personal (each user connects their own).
4. Leave Client ID and Client secret empty. Diskret registers itself with Productive.
5. Under Scope, enter read.
6. Save, then click Check sign-in. Diskret shows the authorization server it found (https://api.productive.io) and the scopes it will ask for.

2. Connect your own account

Go to My connections, click Connect next to Productive, sign in to Productive, choose the organization if asked, and click Allow access. Calls run with your own Productive permissions, so what you cannot see in Productive, Diskret cannot fetch either.

3. Review tools and access

1. On the connector, click Refresh tools. Diskret lists Productive’s tools and suggests which ones read, which change data and which delete it.
2. Open Suggestions and approve or reject the suggested field rules (contacts’ names and emails, people, comments).
3. Open Tools and access and choose which units get which tools. Read tools can be opened broadly; keep tools that log or delete time, create invoices or edit docs closed, or set them to need approval.

Then ask the other users to connect under My connections.

4. Remove the direct Productive connector in Claude

If Productive is also connected to Claude directly, remove that connector, so Productive is reached only through Diskret. See Recommended Claude settings.

Test first in Productive’s sandbox

Productive runs a separate sandbox with its own data. To try write tools without touching live data, add a second connector (e.g. Productive sandbox) with the sandbox URL. Its sign-in and authorization server are separate from production (https://api-sandbox.productive.io).

Caution

Productive’s help article gives the sandbox link as https://mcp-sandbox.productive.io. If that URL does not connect, try https://mcp-sandbox.productive.io/mcp, the same path as production.

Maintenance

• Tokens: Diskret refreshes the access token by itself. If Productive stops accepting it, the user sees Sign in again under My connections.
• Switch organization: disconnect under My connections, then connect again and pick the other organization.
• Revoke access: a user disconnects under My connections; an admin removes the connector to cut off everyone.

Troubleshooting

Error	Likely cause	Fix
Sign-in fails, or Productive refuses access after sign-in	Not on the Ultimate plan, or AI features are off	Check the plan and turn on AI features in Productive
invalid_scope	A scope other than read or write is entered	Use read, or read write
Tools from the wrong organization	The user picked another organization at sign-in	Disconnect and connect again, choosing the right organization
Tools list is empty after sign-in	Tools not refreshed yet	Click Refresh tools on the connector