Connector for Claude

Peaqview for Claude

Ask Claude about your enterprise architecture and business processes. Peaqview gives Claude secure access to your workspace: applications, capabilities, BPMN® processes, obsolescence, risk, governance and transformation scenarios. Claude acts with your own Peaqview account and permissions, and asks before changing anything.

What you can do

Application portfolio

Inventory, ownership, lifecycle, cost and criticality of your applications, rationalization candidates and TIME classification.

Capabilities

Which applications support a capability, where coverage overlaps or is missing, and suggested application and process links.

Business processes

BPMN® processes read step by step, applications supporting each step, process mining results and the architecture impact on a process.

Obsolescence and risk

End-of-life technologies and the applications and processes they put at risk, technical debt, vendor concentration and contract renewals.

Governance

Technology radar, architecture decisions (ADRs) and principles, checked whenever Claude proposes or evaluates a technology.

Transformation

Scenarios, decommissioning impact, migration waves and cost modeling, with interactive views rendered inside Claude.

Requirements

  • A Peaqview account with access to at least one workspace.
  • Claude on the web, desktop or mobile, or Claude Code.
  • If your organization manages Claude centrally, an owner of your Claude organization may need to enable the Peaqview connector first.

Connect Peaqview to Claude

  1. Add the connector. In Claude, open Settings, then Connectors, browse the directory, find Peaqview and select Connect.
  2. Sign in to Peaqview. A Peaqview sign-in page opens. Enter your Peaqview email and password, and your authentication code if your account uses multi-factor authentication.
  3. Choose a workspace. If you belong to several workspaces, pick the one Claude should use. Each connection is tied to one workspace; to switch, disconnect and connect again.
  4. Approve access. The consent page shows the workspace, your account and where you will be sent back to. Check that it is claude.ai, then select Authorize.
  5. Ask a question. Start a conversation and ask about your architecture, for example: "Show me the applications supporting our customer onboarding capability."
Claude Code: add the server with claude mcp add --transport http peaqview <server URL>, using the server URL shown on the Peaqview listing in the Claude directory or provided by your Peaqview administrator, then run /mcp to sign in.

Example questions

"Which applications support our Order-to-Cash process, and which of them reach end of life in the next 18 months?"
"Which capabilities are supported by more than three applications? Suggest rationalization candidates."
"Walk me through the Purchase-to-Pay process step by step and show which application supports each step."
"Can we use MongoDB for the new customer portal? Check our technology radar and architecture decisions."
"We plan to decommission our legacy CRM. Which processes, interfaces and teams are affected?"
"Which vendors are we most dependent on, and which contracts renew in the next six months?"
"Classify our mission-critical applications with the TIME model and explain the outliers."
"Create an ADR for moving our integration layer to event streaming, aligned with our principles."

Permissions and changes

  • Claude only sees and does what your Peaqview role allows in the connected workspace: Administrator, Manager, Contributor or Viewer. Object ownership rules apply exactly as in the application.
  • Every tool is labelled read-only or write. Read-only tools (searches, analyses, reports) can run without confirmation; Claude asks you before running a tool that creates, updates or deletes data.
  • Every change made through Claude is recorded in the object's history with your name and the reason for the change, like any change made in the application.
  • Removing a user from a workspace blocks their Claude access to it immediately, on the next request.

Data handling

  • All traffic between Claude and Peaqview is encrypted with HTTPS/TLS.
  • Authentication uses OAuth 2.0 with PKCE. Access tokens expire after 24 hours; refresh tokens can be used only once and expire after 30 days.
  • Peaqview does not store your conversations with Claude. It receives only the parameters of each tool call and returns the requested workspace data.
  • Some analysis tools use the AI provider your workspace administrator configured in Peaqview. Peaqview does not send your data to any other AI provider.
  • Claude processes tool results under Anthropic's own terms and privacy policy.

See our privacy policy and terms.

Disconnect

In Claude, open Settings, then Connectors, and disconnect Peaqview. Claude stops calling Peaqview immediately. Your Peaqview data is not affected.

Troubleshooting

"Your organization requires Single Sign-On"

Your workspace enforces SSO, and connecting through Claude currently needs a Peaqview password. Contact support@peaqview.com to enable access for your organization.

"User no longer has access to workspace"

Your membership of the workspace you connected to was removed or archived. Ask your Peaqview administrator, then reconnect and choose a workspace you belong to.

Claude asks you to sign in again

This is expected when your session has expired or the connection was renewed on another device. Sign in again; your data and settings are unchanged.

A tool returns "permission denied"

Claude acts with your own Peaqview role. Viewers are read-only, and some objects can only be edited by their owner or an Administrator. Ask your administrator if you need broader rights.

Tools are missing or outdated

Disconnect and reconnect Peaqview in Claude (Settings, then Connectors) to refresh the tool list.

Need help?

Write to us and we will get back to you.

support@peaqview.com