MCP connectors for business data, explained
Model Context Protocol (MCP) is the standard that lets an AI assistant use tools: read a table, create a record, send a message. A "connector" is an MCP server for one product. This explainer is for the person deciding whether to give Claude access to the business's data, and what that actually means.
What a connector is, mechanically
A connector publishes a list of tools with typed inputs: list_projects, create_item, query_items. When you ask Claude something that needs data, it picks a tool, fills the inputs, and the server executes it against the product with your credentials. The model never sees a database; it sees the tool results. Access is exactly what the tools allow, nothing more.
Read, write, or both
| Access | What Claude can do | Typical use |
|---|---|---|
| Read-only | Answer questions from live data: "which orders are late?", "who has not paid?" | Reporting, briefing, support |
| Write | Create and update records: log a lead, move a task, schedule a booking | Operations from chat, automation of routine entry |
| Structure | Create boards, fields, endpoints, automations | Building the system itself, the TaskLite case |
Most connectors from established SaaS products stop at the first two rows. TaskLite's connector covers all three because the product is meant to be shaped by the business, and shaping it is the same kind of tool call as filling it.
The security model that matters
- Whose permissions? The connector should act as the signed-in user, with that user's rights, not as an admin. TaskLite issues Claude a short-lived token scoped to you; it cannot do what you cannot.
- Revocable? Disconnecting must invalidate access immediately. Check for a "revoke" in the product, not just in Claude.
- Audited? Every write through the connector should appear in the product's audit log like any other edit, attributed to you.
- Data residency. The server runs where the product runs; the model provider sees tool inputs and outputs for the conversation. Read the product's privacy policy for the details, TaskLite hosts in the EU.
Three cases where a connector beats a chatbot integration
The Monday briefing
"What needs my attention this week?" A chatbot integration answers from a canned report. A connector queries the actual boards: overdue items, approvals waiting on you, deals without activity. Different answer every Monday, no report to maintain.
Data entry from a conversation
You come back from a site visit and dictate: "new lead, Dana from Levi Bakery, wants a quote for 200 boxes by October, phone 050…". The connector creates the contact, the deal and a follow-up task with the right types. No form, no copy-paste.
Building the system
The case that has no chatbot equivalent: "set up a way to track our supplier deliveries with a portal for the suppliers". The connector creates the boards, the relations, the portal and the automation. Ten minutes instead of a project.
What to check before connecting
- Is the connector published by the product vendor, and does the product document it? Third-party connectors to your business data deserve a harder look.
- Does connecting require OAuth in the product, or pasting a long-lived key? OAuth with short tokens is the better sign.
- Can you see the tool list before approving? A connector with
delete_organizationin it deserves a question. - Where does it work? Some connectors behave differently between Claude Desktop, the web app and Claude Code; the TaskLite connector is tested on all three plus Cursor and Codex.
How TaskLite's connector works
Connect from Claude's connector directory or by URL (https://mcp.tasklite.net/mcp), approve with your TaskLite account, and the 31 tools are available: projects, boards, columns, items, comments, apps and endpoints, automations. The developer manual lists every tool with its inputs, and the TaskLite × Claude page has the setup in three steps.
Frequently asked questions
- Does Claude train on my business data through the connector?
- Tool inputs and outputs are part of your conversation with Claude and are governed by Anthropic's data policy for your plan. Nothing about the connector changes that; TaskLite itself does not send data to any model provider except during your own conversations.
- Can several people in the company use the connector?
- Yes, each with their own TaskLite login and their own permissions. Claude acting for the salesperson cannot see HR boards the salesperson cannot see.
- What happens if I revoke access mid-task?
- The next tool call fails with an authentication error and the conversation stops there. Nothing already written is undone; it is all in the audit log.