Inyett MCP

Inyett MCP is a standardized interface for AI clients and agents. It enables MCP-compatible clients and applications to use Inyett company data.

The MCP service is a protocol layer on top of the Inyett Automation API. It uses the same authentication and product entitlements as the Automation API.

MCP uses Streamable HTTP and is stateless. No local MCP server needs to be installed.

MCP server

https://mcp.inyett.com/mcp

https://mcp-test.inyett.com/mcp

Prerequisites

To connect to Inyett MCP, you need:

Active access to the Inyett Automation API.
Either an Inyett API key or a valid Visma Connect access token.
An MCP client that supports remote MCP over Streamable HTTP.

Authentication

Inyett MCP supports the same credentials as the Automation API:

API key through X-Api-Key.

API key

Send the API key in the X-Api-Key HTTP header.

X-Api-Key: YOUR_INYETT_MCP_KEY

A generic MCP configuration using an API key:

{
  "mcpServers": {
    "inyett": {
      "type": "streamable-http",
      "url": "https://mcp.inyett.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_INYETT_MCP_KEY",
      }
    }
  }
}

Replace:

YOUR_INYETT_MCP_KEY with your API key.
mcp.inyett.com with mcp-test.inyett.com when connecting to the test environment.

Treat the API key as a secret. Never add a real API key to source control or public configuration files.

Client configuration

MCP clients use different configuration formats. Use the following MCP server URL:

https://mcp.inyett.com/mcp

Claude Desktop

Claude Desktop connects to remote MCP servers through Custom Connectors. It does not use a type value such as http or streamable-http for this setup.

Open Settings in Claude Desktop.
Open Connectors.
Select Add custom connector.
Enter the Inyett MCP URL:

https://mcp.inyett.com/mcp

Complete the authentication flow provided by Claude Desktop.

Claude Desktop uses the connector’s remote authentication flow rather than a local claude_desktop_config.json entry for this remote server. Do not add credentials to the MCP URL.

LibreChat

mcpServers:
  inyett:
    type: streamable-http
    url: https://mcp.inyett.com/mcp
    headers:
      X-Api-Key: 'YOUR_INYETT_MCP_KEY'
  

mcpServers:
  inyett:
    type: streamable-http
    url: https://mcp.inyett.com/mcp
    headers:
      Authorization: 'Bearer YOUR_VISMA_CONNECT_ACCESS_TOKEN'
      X-Inyett-Profile-Country: 'SE'

OpenAI Responses API

{
  "type": "mcp",
  "server_label": "inyett",
  "server_url": "https://mcp.inyett.com/mcp",
  "headers": {
    "X-Api-Key": "YOUR_INYETT_MCP_KEY"
  }
}

{
  "type": "mcp",
  "server_label": "inyett",
  "server_url": "https://mcp.inyett.com/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_VISMA_CONNECT_ACCESS_TOKEN",
    "X-Inyett-Profile-Country": "SE"
  }
}

Connection flow

An MCP client normally performs the following operations:

initialize

Establishes the MCP connection.

tools/list

Retrieves the tools available to the credential.

tools/call

Invokes a selected tool.

The MCP server is stateless. The client does not need to manage a local session or connect to a separate local server.

Tools

MCP exposes the following tools:

Tool	Description
`whoami`	Verifies the MCP context and the connection to the Automation API.
`find-company`	Searches for companies by name or other supported search criteria.
`get-company-info`	Retrieves core company information.
`get-company-representatives`	Retrieves representatives and available ownership information.
`get-group-structure`	Retrieves group structures and related company units.

tools/list only shows the company data tools that the credential is entitled to use. whoami is available to authenticated callers.

Company lookup parameters

Tools can use parameters describing the company to retrieve or search for, such as:

Organisation number.
Company name.
Country of the target company.
Search parameters supported by the selected tool.

The profile country is always specified through the API key.

Error responses

HTTP status	Meaning
`400 Bad Request`	The profile country is missing or unsupported.
`401 Unauthorized`	The API key or access token is missing, invalid or expired.
`403 Forbidden`	The credential is valid but does not have access to the requested product or data.
`404 Not Found`	The requested company or resource could not be found.
`429 Too Many Requests`	The request rate limit has been exceeded.

Security recommendations

Store API keys and access tokens in secure secret storage.
Never add credentials to source control.
Do not expose credentials in browser-side client code.
Use production credentials only with the production endpoint.
Use test credentials only with the test endpoint.
Limit the tools made available to an AI agent when the client supports tool allowlists.

Get Started

API

Agentic AI

Use cases

MCP server

Prerequisites

Authentication

Client configuration

Connection flow

Tools

Company lookup parameters

Error responses

Security recommendations

​MCP server

​Prerequisites

​Authentication

​Client configuration

​Connection flow

​Tools

​Company lookup parameters

​Error responses

​Security recommendations

MCP server

Prerequisites

Authentication

Client configuration

Connection flow

Tools

Company lookup parameters

Error responses

Security recommendations