MCP Data1
Run your projects by talking to your AI.
MCP Data1 connects Claude, Cursor, Copilot — any MCP client — to your live Klient PSA data, and does the operations right: create projects and tasks, assign resources, log time, complete work. The Klient data model is built in, so your AI never fumbles a field name or breaks a cascade. This is the headless way to run your Salesforce PSA — your AI acting on the org directly, no chat-bot screen in between.
Everything runs under your own Salesforce login — your permissions, your sharing rules, your audit trail. Every change lands in Projects and Tasks where humans can see and approve it.
Salesforce’s MCP server is great. It just doesn’t know Klient.
The official Salesforce MCP server is genuinely good — it reads and writes across your whole org. It simply doesn’t know Klient. It does general-purpose record work, so it has no way to know that completing a task also closes its assignments, that a project assignment has to exist before a task assignment, or how Klient’s statuses and rate fields fit together. MCP Data1 has the Klient PSA data model built in — so for running your projects, your AI does each operation the way Klient expects, every time.
“General Salesforce access is a commodity. Knowing Klient is the product.”
One install. Your AI. Live Klient PSA.
sf org login web — your real Salesforce login (SSO/MFA)$ sf org login web
// 2. point your MCP client at the local server
{
"command": "node",
"args": ["~/mcp-data1/server.mjs"],
"env": {
"KLIENT_MCP_ORG": "your-org-alias"
}
}
Find, create, update projects; get a health read (status, % complete, tasks by status, overdue) in one call. Status values validated against your org’s picklist; duplicates refused.
Create tasks and subtasks, link dependencies, and complete tasks the correct way: status → Completed and the task’s assignments → Closed. The cascade a generic record edit misses.
Assign people to projects and tasks by name. Assigning to a task auto-creates the project assignment first (correct creation order), and sets the assignment status from the task. Weekly schedules never touch formula rate fields.
Log hours on a task for any day; MCP Data1 finds-or-creates the weekly timesheet and drops the hours in the right day column. Won’t touch a submitted or approved week.
A guarded SOQL/read/create/update escape hatch (Klient objects + Account + Contact only), live picklist lookups, and a Klient-aware schema describe that surfaces the field traps.
Add the Skills that drive MCP Data1.
MCP Data1 is the server. Skills are the guided, lane-specific ways to drive it — each one drives MCP Data1’s tools so you (or your AI) stay in a single lane and do it right. Add the ones your team needs.
Each Skill is its own product. Need one you don’t have yet? Reach out to your Klient Customer Success Manager, or purchase it from the Klient Customers community.
What MCP Data1 covers
What you need to run it
All required — the server won’t start without them. No license key to paste; access is granted at download from the Klient Customers community.
sf org login web — no password or token to manage.31 tools — and not one of them can delete.
No delete operations anywhere. Every write asks for confirmation, runs as your authenticated Salesforce user (your sharing rules and field-level security apply), and is fully auditable.
See all 31 tools ▾
findProject | Resolve a project by Id, exact, or partial name |
listProjects | A filtered project list — the project-level twin of listTasks |
getProjectHealth | Status, % complete, tasks by status, overdue count |
createProject | Create on an Account — resolves names, validates status, refuses dupes |
updateProject | Status / dates / budget / billable / archived |
findTask | Resolve a task by Id/name, optionally within a project |
listTasks | List tasks (open by default — closed statuses excluded) |
createTask | Create a task or subtask — optionally wire dependencies in one call |
updateTask | Update fields (status changes cascade to assignments) |
completeTask | Complete + close the task’s assignments — the cascade a generic update misses |
linkTasks | Finish-to-start dependency with lag days |
addTaskChecklist | Add ordered checklist items to a task |
completeChecklistItem | Check off an item by its text — no record Id needed |
createTaskSection | Create a phase/grouping of tasks (auto-sequenced, dupe-name refused) |
addTaskToSection | Place a task into a section with its order (idempotent) |
createResource | Create a Project Resource — resolves a User, refuses a duplicate |
updateResource | Update a resource: name, active flag, default bill/cost rate |
assignResourceToProject | Assign a person to a project (resolves people to resources) |
assignResourceToTask | Assign to a task — auto-creates the project assignment if missing |
setWeeklySchedule | A week of planned hours on a PA/TA (formula rate fields protected) |
updateProjectAssignment | Update a PA: status, dates, rates, notes |
updateTaskAssignment | Update a TA: status, dates, rates, estimated hours, hold |
updateWeeklySchedule | Edit hours of an existing week — only the days you pass change |
addTimeEntry | Add a new time entry on a task for a day — weekly timesheet auto-created |
updateTimeEntry | Edit an existing entry by Id — overwrite that day’s hours/comment |
queryRecords | SOQL read (allowlisted objects) |
getRecord | Single-record read by Id |
createSObject | Generic create on an allowlisted object (formula fields & OwnerId rejected) |
updateSObject | Generic update (formula fields & OwnerId rejected) |
getPicklistValues | Live picklist values from the org |
describeKlientObject | Object schema + Klient field traps, formula warnings, status mappings |
Built to be safe in your org
One-time. Per company. No subscription.
Questions, answered
MCP for Salesforce PSA is an open Model Context Protocol server that lets any AI client (Claude, Cursor, Copilot) act directly on your Klient PSA data in Salesforce — creating projects and tasks, assigning resources, and logging time under your own login. MCP Data1 is Klient’s MCP server for project operations.
You can — for general Salesforce work it’s great, and the official servers (now generally available) both read and write. The one thing they don’t have is Klient: they do general-purpose record work, so they don’t know Klient’s cascades, creation order, status mappings, or which fields are formulas. MCP Data1 adds exactly that — the Klient PSA data model, built in — so your AI runs projects the way Klient expects. It’s the Klient-aware companion to the Salesforce MCP, not a replacement.
Any MCP-compatible client — Claude Desktop/Code, Cursor, Copilot, others.
No. It runs on your machine, against your org, under your Salesforce login. Klient hosts nothing.
No deletes exist; writes need confirmation; formula fields and ownership are protected; everything is scoped to the Klient model and lands as auditable records.
No — MCP Data1 is an attended, headless copilot for a person in a chat; the Agentforce agents are unattended workers. Same destination: the project.
No.
One-time, perpetual, per company. No subscription.