# How to connect Claude to Deltek Costpoint

> Source: https://netray.co/integrations/deltek-costpoint-claude
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Integrations

## Short answer

Connect Claude to Costpoint through a read-only MCP server that wraps a replica or Costpoint's supported interfaces, then use Claude through the Anthropic API, AWS Bedrock or Google Vertex depending on your cloud and compliance boundary. When data must stay on your own hardware, run an open-weight model behind the same MCP tools.

## System

Deltek Costpoint

## Capability

claude

## Intro

Teams on Costpoint often come to Claude for the writing and reasoning quality: explaining a cost variance, summarizing a long contract modification, or drafting a response to an auditor request. The question is how to give it live, correct data without handing over the keys to the ledger.

The pattern that holds up is the same one used everywhere: do not let the model query the database. Expose a small set of named tools, each read-only at first, through the Model Context Protocol. Claude, whether in a desktop client, a browser connector or your own application, calls those tools and reasons over what comes back.

Where Claude runs matters as much as how it connects. For some contractors a major cloud region with the right authorizations is acceptable; for others only a private deployment is.

## Use Cases

### Auditor request drafting

**Description:** Claude reads the request, calls tools to pull the relevant project cost detail, and drafts a response with the support schedule referenced, for the contracts team to review.

### Contract modification impact summary

**Description:** A modification PDF plus current funding and billing data lets Claude explain what changed for a project and which Costpoint fields need updating, without making the updates.

### Long-context ledger review

**Description:** Claude's large context handles an extended project cost listing and highlights unusual postings, with each flagged line cited by key so the analyst can find it.

### Indirect rate story

**Description:** A controller asks why the fringe or overhead rate moved. Claude calls a pool variance tool, compares periods and writes the narrative with the account-level drivers.

### Onboarding assistant for new analysts

**Description:** New staff ask how a charge code, labor category or billing term is used, and Claude answers from your internal procedures plus read-only lookups.

## System Surface

A reporting replica or scheduled extract of Costpoint tables, the safest source for MCP tools. Core entities include project, account, organization, employee and timesheet lines; confirm exact table and column names in your version's data dictionary.

Costpoint web services and REST style endpoints where your license and deployment allow them, usable as the MCP server's backend instead of SQL.

Report outputs and saved queries, which can be turned into MCP tools that return fixed shapes, easier to validate than generated SQL.

Costpoint role and application security. The MCP server should authenticate the user and apply equivalent limits, or at least restrict by project and organization set.

Document stores for contracts and modifications, usually outside Costpoint (SharePoint or a file share), which Claude can read through a separate document tool.

## How It Works

### Decide where Claude may run

**Detail:** Options include Anthropic's API, Claude through AWS Bedrock or Google Vertex AI in your cloud tenancy, or no Claude at all for the most restricted data. Match this to your authorization requirements before building.

### Build the MCP server

**Detail:** Implement tools such as get_project_summary, get_funding_status, list_cost_by_account, get_pool_rates. Return JSON with record keys and period identifiers.

### Choose transport and auth

**Detail:** Use stdio for a single-user desktop test and streamable HTTP behind your gateway for shared use, with OAuth or SSO identity passed to the server.

### Write precise tool descriptions

**Detail:** State units, fiscal period semantics and posted versus unposted. Claude relies on these descriptions to choose and interpret tools correctly.

### Test against a closed month

**Detail:** Ask ten questions whose answers you know, and compare every number to the ledger before widening access.

### Roll out by group

**Detail:** Start with finance and contracts, add program managers later with narrower project scopes.

## Example Flows

### Answer an auditor question with support

**Trigger:** Contracts receives an audit request about indirect cost allocation for a fiscal year

**Steps:**

- Analyst pastes the request into Claude with the MCP connector enabled.
- Claude calls get_pool_rates and list_cost_by_account for the year.
- It drafts a response describing the allocation base and attaches a table.
- Analyst verifies figures and sends through the normal review chain.

**Result:** A reviewed draft with cited numbers, in a fraction of the manual assembly time.

### New modification intake

**Trigger:** A contract modification PDF arrives

**Steps:**

- Claude reads the PDF from the document store.
- It calls get_funding_status for the affected project.
- It lists the changes to value, period and clauses.
- It produces a checklist for the administrator to apply in Costpoint.

**Result:** Fewer missed updates, with a person still making the changes in the system of record.

## On Prem

Claude is not distributed for on-premises installation, so a strictly air-gapped Costpoint site cannot run it. The practical options are Claude via a cloud provider region that meets your authorization needs, or an open-weight model on your own GPUs that speaks the same MCP tool protocol. Because MCP separates the tools from the model, you can build the Costpoint server once and point it at Claude where permitted and at a private model where not. Many contractors use both: Claude for non-controlled drafting, a private model for anything touching cost and pricing data or CUI. Confirm cloud authorizations with your own compliance lead rather than assuming a given region qualifies.

## Security

- Keep the MCP server read-only until the read path has been validated and an approval workflow exists for anything else.
- Authenticate users to the MCP server and enforce project and organization scoping server-side.
- Review the provider's data retention and training terms for your plan, and select zero-retention settings where available.
- Do not place secrets or connection strings in tool descriptions or prompts.
- Log tool calls with user, parameters and row counts, and alert on unusually broad pulls.

## Options

### Claude with a community or vendor MCP connector

**Fit:** Exploration on non-sensitive data; check maintenance and security of any third-party connector.

**Effort:** Days to evaluate

### Custom MCP server built in-house

**Fit:** Teams with Costpoint database knowledge and a developer comfortable with Python or TypeScript.

**Effort:** Two to six weeks for a read-only tool set

### Partner-built MCP layer with private model fallback

**Fit:** Mixed sensitivity data and a need for audit trails and approval gates.

**Effort:** Scoped pilot, then expand tools

## Pitfalls

- Vague tool descriptions. If posted versus unposted is not stated, Claude may mix them and give a plausible wrong total.
- Returning thousands of rows from a tool. Paginate and aggregate in the server so context is spent on reasoning.
- Treating cloud model availability as a compliance decision. It is a technical fact, not an authorization.
- Letting users share one connector token, which erases per-user scoping and audit identity.

## Faq

### Does Claude have a built-in Deltek Costpoint connector?

**Answer:** Not that we can point you to as a standard product. Claude connects to systems through MCP servers, so you or a partner build or adopt one for Costpoint. Check Deltek's marketplace and your account team in case something has been released for your version.

### Can Claude run inside our firewall?

**Answer:** Claude itself is accessed as a service, including through some major cloud providers, so a fully isolated network cannot run it. Where isolation is required, run an open-weight model locally behind the same MCP tools and accept some capability trade-off.

### Is Claude better than ChatGPT for this?

**Answer:** It depends on your tasks, and results vary by prompt and tool design. Both can use the same facade. Evaluate both on your own ten test questions, since tool quality and governance matter far more than which model name is behind them.

### Will Claude change anything in Costpoint?

**Answer:** Not if the MCP tools are read-only, which is how to start. Any write capability should be a separate, narrow tool behind approval, and many sites keep Costpoint posting as a human step permanently.

### What about CMMC?

**Answer:** CMMC applies to your environment, not to a model. Your obligations depend on whether the data is CUI and how the service handles it. Involve your compliance assessor before sending covered data to any cloud model; a private deployment avoids the question.

## Search terms

deltek costpoint claude, claude for deltek costpoint, connect claude to costpoint, costpoint mcp claude, claude govcon erp, anthropic claude costpoint, claude bedrock costpoint data, costpoint claude integration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json