Skip to content
CSFaaS
Resources
DocumentationAPI referenceMCP
DocumentationDocs
ResourcesDocumentationProduct guides & methodologyAPI referenceEndpoints, models & examplesMCPConnect your AI clientOpen app
Open app
Documentation
Open appAPI referenceMCPContact support

Loading documentation…

Documentation
Documentation
Open appAPI referenceMCPContact support

Search documentation

0 saved guides. Search titles and guide content.

Find a guide by title or search its content. Save useful guides from their page tools to find them here.

↑ ↓ to navigate · Enter to openEsc to close
14. API & MCP Settings · CSFaaS Docs
Skip to content
CSFaaS
Resources
DocumentationAPI referenceMCP
DocumentationDocs
ResourcesDocumentationProduct guides & methodologyAPI referenceEndpoints, models & examplesMCPConnect your AI clientOpen app
Open app
Documentation
  • 1.Welcome to CSFaaS
  • 2.Discover CSFaaS
  • 3.CyberSecurity Risk Management - Fundamentals & Guidelines
  • 4.Prepare your organisation
  • 5.Workspace settings and configuration
    • 1.Manage workspace identity and ownership
    • 2.Framing settings
    • 3.Catalogue configuration
    • 4.Configure notification events
    • 5.Billing, seats and workspace limits
    • 6.Manage workspace members
    • 7.Define and assign workspace roles
    • 8.Configure framework and policy approvals
    • 9.Set priority SLAs for risk demands
    • 10.Configure the risk and impact matrices
    • 11.Manage workspace tags
    • 12.Choose whether evidence files may be uploaded
    • 13.Read workspace data with the API
    • 14.Manage API and MCP access
    • Workspace settings overview
  • 6.Prepare your assets and key components
  • 7.Manage your Supply Chain
  • 8.Manage your frameworks
  • 9.Manage your policies
  • 10.Manage your controls
  • 11.Operational Use of the CSFaaS Risk Management Solution
  • 12.Forms
  • 13.Manage your Evidences
  • 15.Help and support
  • 16.Put the documentation into practice
Open appAPI referenceMCPContact support

Loading documentation…

Documentation
Documentation
  • 1.Welcome to CSFaaS
  • 2.Discover CSFaaS
  • 3.CyberSecurity Risk Management - Fundamentals & Guidelines
  • 4.Prepare your organisation
  • 5.Workspace settings and configuration
    • 1.Manage workspace identity and ownership
    • 2.Framing settings
    • 3.Catalogue configuration
    • 4.Configure notification events
    • 5.Billing, seats and workspace limits
    • 6.Manage workspace members
    • 7.Define and assign workspace roles
    • 8.Configure framework and policy approvals
    • 9.Set priority SLAs for risk demands
    • 10.Configure the risk and impact matrices
    • 11.Manage workspace tags
    • 12.Choose whether evidence files may be uploaded
    • 13.Read workspace data with the API
    • 14.Manage API and MCP access
    • Workspace settings overview
  • 6.Prepare your assets and key components
  • 7.Manage your Supply Chain
  • 8.Manage your frameworks
  • 9.Manage your policies
  • 10.Manage your controls
  • 11.Operational Use of the CSFaaS Risk Management Solution
  • 12.Forms
  • 13.Manage your Evidences
  • 15.Help and support
  • 16.Put the documentation into practice
Open appAPI referenceMCPContact support

Search documentation

0 saved guides. Search titles and guide content.

Find a guide by title or search its content. Save useful guides from their page tools to find them here.

↑ ↓ to navigate · Enter to openEsc to close
Documentation5. Workspace settings and configuration14. API & MCP Settings
CSFaaS
DocumentationV1 - Archived guide

14. API & MCP Settings

Updated 2 months ago3 min read
V1V2V3

5. Workspace settings and configuration

Archived guide · V1View current version

CSFaaS exposes a Platform API and an MCP server so you can bring your own AI (like Claude) and connect it to your workspace data, or read your compliance data from your own scripts and tools. The API & MCP section of Workspace Settings is where you manage that access. It is included free with every seat.

The API & MCP section: API keys and workspace API access

1. What You Get#

  • A read-only REST API at api.csfaas.com covering frameworks, policies, controls, risks, demands, audits, systems, third parties, forms and evidences. The full interactive reference lives at api.csfaas.com/v1.
  • An MCP server at mcp.csfaas.com, so AI assistants such as Claude can query your compliance programme conversationally. Its overview and setup guide live at that address.

Both surfaces are read-only and every request is scoped by permissions: a key can never read more than the roles it carries allow.


2. Workspace API Access#

The Workspace API access switch is the master kill switch for the Platform API and MCP across this workspace. When off, every API key stops working until you turn it back on; the keys themselves are kept, so re-enabling restores integrations without re-issuing anything.

Changing the switch requires the Workspace settings edit permission.


3. API Keys#

Access is authenticated by API keys. Three properties define the model:

  • Keys act as a user: an admin binds a key to a workspace member, and the key reads exactly what that user can, nothing more. It follows the user's live permissions, so demoting or removing the user immediately narrows or cuts off the key.
  • Keys are created by administrators: only workspace admins, or members with Settings access, can create API keys, and creating one requires two-factor authentication on your account. Give the key a recognisable name (for example "Claude on my laptop") and choose the member it acts as.
  • The secret is shown once: copy the key when it is revealed; for your security it will not be shown again. If you lose it, revoke it and create a new one.

The section lists Your API keys and All workspace keys (every key issued by members of this workspace), with creation and last-used dates. Any key can be revoked, which immediately cuts off whatever uses it, or deleted entirely. Both actions are irreversible.

Note: API keys cannot be created in the demo workspace. Create your own workspace to connect the API.


4. Connecting#

The Connect quickstart card gives you everything needed to point a client at the API:

  • The base URL and the authentication header to send with each request.
  • A ready-to-copy request that answers "who am I?", to verify a key works.
  • An MCP server configuration block to paste into your MCP client (for example Claude Desktop), replacing the placeholder with your API key.

The Documentation cards link to the two hosted references: the full Platform API reference (authentication, permission model, endpoints and examples) and the MCP guide with the tool catalogue and setup instructions for Claude, Cursor or any MCP client.

Warning: treat an API key like a password. Never share it, and revoke any key you suspect has leaked.

Privacy note. Personal details in this revision have been removed, masked or replaced for privacy. The original is retained privately.

Read this guide onlinehttps://www.csfaas.com/documentation/5-workspace-settings-configuration/api-mcp-settings/?revision=v1
Previous13. Read workspace data with the API
NextWorkspace settings overview
CSFaaS documentationNeed help?
ON THIS PAGE
Overview1. What You Get2. Workspace API Access3. API Keys4. Connecting
PAGE TOOLSBack to top