# Pascal MCP Servers

Source: https://www.trypascal.io/platform/mcp-servers

Your business, available to AI.

Give compatible AI clients the tools and context to work with your business. Assemble an MCP server visually, test what it can do, and keep access under your control.

## Capabilities

### Build without server code

Start from a knowledge, analyst, operations, or integration template—or a blank server. Give it a purpose and choose the capabilities it needs in a guided builder.

### Bring tools and context together

Combine callable operations, readable resources, and reusable prompts. AI clients get a clear way to find information and take the next permitted step.

### Reuse knowledge deliberately

Import a specific Context Package version. Inspect compatible items and limitations, then review the changes before moving to a newer version.

### Test the actual saved draft

Choose a capability, enter inputs in a form, and run it as an available test identity. Inspect the response and access decision before making a release decision.

### Keep access in the business

Scope server access to workspace roles and teams. Each request still follows current membership, capability permissions, connection availability, and required approvals.

### Release with a stable address

When hosting is enabled, publish an immutable version behind one stable endpoint. Make changes in the draft, release deliberately, and return to an earlier released version when needed.

## Connected context

Integrations connect the systems behind your tools. Dynamic Context supplies reusable knowledge packages. MCP Servers makes selected capabilities available through the Model Context Protocol, while the Pascal products behind them keep control of their data and actions.

- Tools: selected business operations with their existing inputs, permissions, and approval requirements
- Resources: readable knowledge and data supplied by the products that own them
- Prompts: reusable instructions with named inputs and linked resources
- Context imports: exact package versions with visible compatibility and deliberate upgrades

## Controls and permissions

Your workspace decides who can reach the server; each capability decides what that person can do. Connected-account credentials remain private. Draft authoring and friendly tests are available before hosted access. Remote client connections and publication require the deployment’s OAuth interoperability checks and hosting to be enabled.

## Example

A customer-success manager is preparing for a Northstar renewal. The team’s MCP server brings together an account lookup, the customer playbook, and a reusable briefing prompt. A compatible AI client can use those selected capabilities to prepare the conversation. Any later action still needs its own permissions and approvals.

## Workflow

### Select the work the client can do

- The Customer success server includes Find customer accounts, a customer playbook, and an account-brief prompt. The selected lookup retains its read permission; adding it to a server does not widen access.

### Choose who can use it

- Review workspace sign-in and limit the server to the Customer success team. The server’s audience and the permissions of each capability both apply when a request arrives.

### Check the result before release

- Test Find customer accounts with Northstar as the input. The saved draft returns the illustrative account and an access decision. A successful draft test does not establish a hosted client connection.

## Next steps

Start with one team, one client, and the tools and knowledge the job needs. We’ll help you define the scope and verify the connection before rollout.

- [Plan your MCP server](https://www.trypascal.io/contact)
- [Pascal Work](https://www.trypascal.io/solutions/pascal-work)