Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Artesa MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read customers, assignments, staff, time entries and absences; create customers in Artesa.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http artesa-mcp-by-usefulapi https://artesa.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# artesa_list_customers, artesa_get_customer, artesa_create_customer and 15 more
Artesa MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http artesa-mcp-by-usefulapi https://artesa.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List customers (private persons or companies that assignments are carried out for). Filter by company name, number or external id. Artesa API: GET /v2/customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_name | string | no | Filter by company name. |
| number | string | no | Filter by customer number. |
| external_id | string | no | Filter by the external id from your other system. |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
Get one customer with its phones, emails, URLs and billing address. Artesa API: GET /v2/customers/{customerUuid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_uuid | string | yes | The customer uuid (from the matching list tool). |
Create a new customer record (company or private person). Not safe to retry: a retry creates a second customer. Artesa API: POST /v2/customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_name | string | no | Company name (leave empty for a private person). |
| first_name | string | no | First name. |
| surname | string | no | Surname. |
| external_id | string | no | Id from your other system. |
| emails | array | no | Email addresses. |
| telephones | array | no | Phone numbers. |
List assignments (orders/jobs) with their customer, project, type, responsible user and status. Artesa API: GET /v2/assignments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_uuid | string | no | Only assignments of this customer uuid. |
| project_uuid | string | no | Only assignments in this project uuid. |
| type_uuid | string | no | Only assignments of this assignment type uuid. |
| responsible_user_uuid | string | no | Only assignments for this responsible user uuid. |
| status_uuid | string | no | Only assignments with this status uuid. |
| name | string | no | Filter by assignment name. |
| number | string | no | Filter by assignment number. |
| external_id | string | no | Filter by external id. |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
Get one assignment with its details. Artesa API: GET /v2/assignments/{assignmentUuid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| assignment_uuid | string | yes | The assignment uuid (from the matching list tool). |
List work steps (appointments and events) of assignments, optionally in a time window. Artesa API: GET /v2/assignment-events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| assignment_uuid | string | no | Only events of this assignment uuid. |
| type_uuid | string | no | Only events of this assignment event type uuid. |
| group_uuid | string | no | Only events in this assignment event group uuid. |
| name | string | no | Filter by event name. |
| starts_from | string | no | Events starting at or after this time, ISO 8601 (e.g. 2026-03-01T00:00:00Z). |
| starts_to | string | no | Events starting at or before this time, ISO 8601 (e.g. 2026-03-01T00:00:00Z). |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
Get one assignment event (work step). Artesa API: GET /v2/assignment-events/{assignmentEventUuid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| assignment_event_uuid | string | yes | The assignment event uuid (from the matching list tool). |
List projects that group assignments. Artesa API: GET /v2/projects.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | no | Filter by project number. |
| external_id | string | no | Filter by external id. |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
Get one project. Artesa API: GET /v2/projects/{projectUuid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_uuid | string | yes | The project uuid (from the matching list tool). |
List users (staff members) with their role. Filter by name, email or role. Artesa API: GET /v2/users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role_uuid | string | no | Only users with this role uuid. |
| full_name | string | no | Filter by full name. |
| string | no | Filter by email address. | |
| short_name | string | no | Filter by short name. |
| staff_number | string | no | Filter by staff number. |
| external_id | string | no | Filter by external id. |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
Get one user (staff member). Artesa API: GET /v2/users/{userUuid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_uuid | string | yes | The user uuid (from the matching list tool). |
List recorded time entries (work time) per user, assignment or event, optionally in a time window. Artesa API: GET /v2/time-entries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_uuid | string | no | Only entries of this user uuid. |
| assignment_uuid | string | no | Only entries on this assignment uuid. |
| event_uuid | string | no | Only entries on this assignment event uuid. |
| type_uuid | string | no | Only entries of this time entry type uuid. |
| day_status | string | no | Filter by the day status of the time sheet. |
| starts_from | string | no | Entries starting at or after this time, ISO 8601 (e.g. 2026-03-01T00:00:00Z). |
| starts_to | string | no | Entries starting at or before this time, ISO 8601 (e.g. 2026-03-01T00:00:00Z). |
| external_id | string | no | Filter by external id. |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
List absences (holidays, sick days and similar) of users in a time window. Artesa API: GET /v2/user-absences.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_uuid | string | no | Only absences of this user uuid. |
| type_uuid | string | no | Only absences of this user absence type uuid. |
| status | string | no | Filter by absence status. |
| starts_from | string | no | Absences starting at or after this time, ISO 8601 (e.g. 2026-03-01T00:00:00Z). |
| starts_to | string | no | Absences starting at or before this time, ISO 8601 (e.g. 2026-03-01T00:00:00Z). |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
List weekly time sheets per user, with their status. Artesa API: GET /v2/time-sheet-weeks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_uuid | string | no | Only time sheets of this user uuid. |
| week_start | string | no | Week start date (yyyy-mm-dd). |
| status | string | no | Filter by time sheet status. |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
List the assignment status types (Auftragsstatus) your company uses. Artesa API: GET /v2/assignment-status-types.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Filter by status name. |
| category | string | no | Filter by status category. |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
List the assignment types (Auftragstypen) your company uses. Artesa API: GET /v2/assignment-types.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
List gangs (work crews or teams) of your company. Artesa API: GET /v2/gangs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Filter by gang name. |
| external_id | string | no | Filter by external id. |
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
List the user roles (Benutzerrollen) of your company. Artesa API: GET /v2/roles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Zero-based page index (default 0). |
| size | integer | no | Items per page, 1 to 20 (default 10). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Artesa MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| artesa_list_customers | no tags | |
| artesa_get_customer | no tags | |
| artesa_create_customer | state-write | state-write: declares destructiveHint: true |
| artesa_list_assignments | no tags | |
| artesa_get_assignment | no tags | |
| artesa_list_assignment_events | no tags | |
| artesa_get_assignment_event | no tags | |
| artesa_list_projects | no tags | |
| artesa_get_project | no tags | |
| artesa_list_users | no tags | |
| artesa_get_user | no tags | |
| artesa_list_time_entries | no tags | |
| artesa_list_user_absences | no tags | |
| artesa_list_time_sheet_weeks | no tags | |
| artesa_list_assignment_status_types | no tags | |
| artesa_list_assignment_types | no tags | |
| artesa_list_gangs | no tags | |
| artesa_list_roles | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.5.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Artesa MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.