Back to technical overview

MCP documentation

TapInn in Claude through MCP
Connection and control.

Connect TapInn to Claude, understand data sharing, and review proposed changes before approval.

Details

Explained in practice.

Connect

Add TapInn as a custom connector in Claude with server URL https://www.tapinn.no/api/tap/mcp. Sign in on TapInn’s consent page. Check the organization, client and permissions before granting access. An authorized administrator must resolve a policy denial.

Check access

Ask for published shifts on a specific date or timesheets you can access. An empty result is not an error. The observed Claude connection also requests payroll summary and therefore requires a tenant administrator. Employee onboarding with narrower scopes is not yet verified; do not expand an employee’s role to bypass this limitation.

Approve changes

Write tools stage proposals. Nothing changes in TapInn until a human approves through TapInn’s approval card or secure browser flow. Saying “yes” in chat is not that approval. Proposals are checked again before execution; changed data may require a new proposal.

Shift log: tapinn_shift_log_create

This tool proposes an organization shift log and requires mcp:operations:write and the scheduling module. shiftDate is required in YYYY-MM-DD format. body is required with 1–4000 characters. Optional locationId and scheduleId UUIDs must reference permitted organization records. category is handover, deviation or note (default: handover). Optional deviations has at most 50 items, each with text of 1–500 characters and optional resolved (default: false). The result is an approval proposal, not a created log. Invalid input, missing scope, a disabled module or unavailable references are rejected.

Conversation data

TapInn responses are shared with Claude and become part of the conversation. Pseudonyms do not guarantee anonymity or EU-only processing. Use the connection under your organization’s approved agreements and data policy. Sensitive reviews and file downloads may open in TapInn with a separate access check.

Refresh or disconnect

If access expires, reconnect and review consent again. To revoke access, sign in at https://www.tapinn.no/tap/mcp/connections, find the Claude connection and disconnect it. Then remove the connector in Claude. Removing it only in Claude does not prove server access was revoked. Disconnecting does not erase previously shared conversation content.

Troubleshooting

Check the organization, role, modules and approved AI policy. Send the error code, time and a description to TapInn support. Never send passwords, OAuth codes or access tokens. Never ask the assistant to bypass a denial or approval.

Contact

Need a concrete answer?

If you are evaluating TapInn or need clarification on workflow, privacy or technical frameworks, you can contact us directly.

hei@tapinn.no