Itcons.app MCP Server
Connects AI assistants to the Itcons.app business operations platform for managing work reports, work orders, projects, clients, and users. It supports both local stdio and remote HTTP modes, enabling querying, searching, and creating operational data with secure authentication.
README
Itcons.app MCP Server
Model Context Protocol server for connecting AI assistants to Itcons.app.
Itcons.app is a business operations platform for managing work reports, work orders, projects, clients, users, and related operational resources. It is designed to help teams digitize field and office workflows around daily reports, assignments, task tracking, and service execution.
This package can run in two modes:
- Local
stdiomode for clients such as Codex, Claude Desktop, and other local MCP hosts. - Remote HTTP mode for hosted MCP clients such as ChatGPT Apps or other clients that require a public HTTPS MCP endpoint.
With this MCP server, an assistant can query Itcons.app data, search work reports and work orders, list operational catalogs such as statuses, users, resources, projects, and clients, and create supported Itcons.app records when the configured user has permission to do so.
Features
- Authenticate with
POST /api/login_check. - Use Bearer authentication for Itcons.app API calls.
- Resolve the API base URL from
ITCONS_DOMAIN. - List statuses, users, resources, clients, projects, work order types, and work report models.
- Search work reports and work orders.
- Create clients, projects, users, and work orders.
Webhooks are intentionally not included in this MCP server. The remote HTTP mode is for MCP client traffic, not inbound Itcons.app webhook delivery.
Installation
From npm:
npm install -g @itcons-app/mcp
From this repository:
npm install
npm run check
If Node was installed with Homebrew and node/npm are not in your PATH, use:
/opt/homebrew/opt/node/bin/npm install
/opt/homebrew/opt/node/bin/npm run check
Configuration
The local stdio server reads Itcons.app credentials from environment variables.
ITCONS_DOMAIN=demo
ITCONS_USERNAME=user@example.com
ITCONS_PASSWORD=change-me
ITCONS_TIMEZONE=Europe/Madrid
For https://demo.itcons.app, set:
ITCONS_DOMAIN=demo
You may use an existing Bearer token instead of username/password:
ITCONS_DOMAIN=demo
ITCONS_TOKEN=ey...
ITCONS_API_BASE_URL is optional. If omitted, the server uses:
https://ITCONS_DOMAIN.itcons.app/api
MCP Client Example
Example configuration using a globally installed package:
{
"mcpServers": {
"itcons-app": {
"command": "itcons-app-mcp",
"env": {
"ITCONS_DOMAIN": "demo",
"ITCONS_USERNAME": "user@example.com",
"ITCONS_PASSWORD": "change-me",
"ITCONS_TIMEZONE": "Europe/Madrid"
}
}
}
}
Remote HTTP Server
Start the remote MCP server:
PORT=3000 \
HOST=127.0.0.1 \
ITCONS_MCP_PUBLIC_URL=https://mcp.example.com \
ITCONS_OAUTH_CLIENT_ID=itcons-app-chatgpt \
ITCONS_OAUTH_CLIENT_SECRET=change-me \
npm run start:http
The remote server exposes:
- MCP Streamable HTTP endpoint:
https://mcp.example.com/mcp - SSE-compatible endpoint:
https://mcp.example.com/sse - OAuth authorize URL:
https://mcp.example.com/oauth/authorize - OAuth token URL:
https://mcp.example.com/oauth/token - OAuth dynamic client registration URL:
https://mcp.example.com/oauth/register - Health check:
https://mcp.example.com/health
For ChatGPT's "Create app" screen, use the public MCP URL:
https://mcp.example.com/mcp
If a client specifically asks for an SSE URL, use:
https://mcp.example.com/sse
When the user connects the app, the OAuth login page asks for their Itcons.app email and password. If ITCONS_DOMAIN_LOOKUP_URL is configured, the page tries to detect the Itcons.app domain from the email; otherwise the user can type the domain manually. The server validates those credentials with Itcons.app and stores an in-memory session token for subsequent MCP calls.
Example configuration using a local checkout:
{
"mcpServers": {
"itcons-app": {
"command": "node",
"args": [
"/absolute/path/to/itcons-app-mcp/src/index.js"
],
"env": {
"ITCONS_DOMAIN": "demo",
"ITCONS_USERNAME": "user@example.com",
"ITCONS_PASSWORD": "change-me",
"ITCONS_TIMEZONE": "Europe/Madrid"
}
}
}
}
Tools
Read-only tools:
itcons_check_connectionitcons_list_workorder_typesitcons_list_work_report_modelsitcons_list_projectsitcons_list_clientsitcons_list_statusesitcons_list_usersitcons_list_resourcesitcons_search_workordersitcons_list_pending_workordersitcons_search_work_reportsitcons_list_work_reports_by_dateitcons_list_today_work_reports
Create tools:
itcons_create_workorderitcons_create_useritcons_create_projectitcons_create_client
Tool annotations:
- Read-only tools set
readOnlyHint: true,destructiveHint: false, andopenWorldHint: true. - Create tools set
readOnlyHint: false,destructiveHint: false, andopenWorldHint: true.
Environment Variables
| Variable | Required | Description |
|---|---|---|
ITCONS_DOMAIN |
Yes | Installation subdomain. For https://demo.itcons.app, use demo. |
ITCONS_USERNAME |
Yes, unless ITCONS_TOKEN is set |
Itcons.app username or email. |
ITCONS_PASSWORD |
Yes, unless ITCONS_TOKEN is set |
Itcons.app password. |
ITCONS_TOKEN |
No | Existing Bearer token. If set, login is skipped. |
ITCONS_API_BASE_URL |
No | Alternative API base URL. |
ITCONS_TIMEZONE |
No | Time zone used by itcons_list_today_work_reports. Defaults to Europe/Madrid. |
PORT |
No | HTTP server port. Defaults to 3000. |
HOST |
No | HTTP server bind host. Defaults to 127.0.0.1. |
ITCONS_MCP_PUBLIC_URL |
Yes for remote mode | Public HTTPS origin, for example https://mcp.example.com. |
ITCONS_MCP_PATH |
No | Remote MCP endpoint path. Defaults to /mcp. |
ITCONS_MCP_SSE_PATH |
No | SSE-compatible endpoint path. Defaults to /sse. |
ITCONS_MCP_ALLOWED_HOSTS |
Recommended for remote mode | Comma-separated allowed Host headers, for example mcp.example.com. |
ITCONS_OAUTH_CLIENT_ID |
No | OAuth client ID expected by the remote server. Defaults to itcons-app-chatgpt. |
ITCONS_OAUTH_CLIENT_SECRET |
Recommended for remote mode | OAuth client secret expected by the remote server. |
ITCONS_OAUTH_CLIENTS_FILE |
Recommended for public apps | JSON file used to persist dynamically registered OAuth clients. |
ITCONS_DOMAIN_LOOKUP_URL |
No | Endpoint used to detect the Itcons.app domain from an email. Defaults to https://auto.itcons.app/webhook/my-domain. |
ITCONS_HTTP_AUTH_DISABLED |
No | Set to 1 only for local HTTP smoke tests. Disables remote MCP bearer auth. |
Notes
- Work order pending status is
4. itcons_search_workordersfetches/workordersand applies filters locally.itcons_list_work_reports_by_datefilters on thedatefield returned by/2.0/partes.itcons_create_workordersendsstatus: 4andisArchived: 0.itcons_create_usersends an array payload to/2.0/users, matching the current API.itcons_create_clientsends an array payload to/clientsand returns the first array item when applicable.
Development
Run syntax checks:
npm run check
Run a local MCP discovery smoke test:
npm run smoke
Run a local HTTP MCP smoke test:
npm run smoke:http
Run a live read-only HTTP smoke test against Itcons.app:
ITCONS_DOMAIN=demo \
ITCONS_USERNAME=user@example.com \
ITCONS_PASSWORD=change-me \
npm run smoke:http:live
Run a live OAuth smoke test that simulates a ChatGPT-style connection:
ITCONS_DOMAIN=demo \
ITCONS_USERNAME=user@example.com \
ITCONS_PASSWORD=change-me \
npm run smoke:oauth:live
Run a live read-only smoke test against Itcons.app:
ITCONS_DOMAIN=demo \
ITCONS_USERNAME=user@example.com \
ITCONS_PASSWORD=change-me \
npm run smoke:live
Publish the public npm package:
npm publish --access public
Security
Do not commit .env files or real credentials. The package excludes .env, node_modules, and debug logs from npm publication.
Create tools perform real writes in Itcons.app. Use them only with credentials and installations where the MCP client is allowed to make changes.
The built-in remote OAuth implementation stores authorization codes and access tokens in memory. Use a single Node.js process for the first deployment, or replace the in-memory maps with persistent storage such as Redis before running multiple replicas.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.