A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Elvanto 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.
23
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Look up people, groups, service rosters, songs, follow-up flows and giving in Elvanto.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http elvanto-mcp https://elvanto.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# elvanto_list_people, elvanto_search_people, elvanto_get_person and 20 more
Elvanto costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 elvanto-mcp https://elvanto.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
23 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 people in the church database, optionally filtered by category and by suspended / contact / archived status. Paginated (the response carries page, per_page, total). Elvanto: people/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| category_id | no | Only people in this people category id (or any of these ids). | |
| suspended | string | no | yes = only suspended people, no = exclude them. Default all. |
| contact | string | no | yes = only contacts, no = exclude contacts. Default all. |
| archived | string | no | yes = only archived people, no = exclude them. Default all. |
| fields | array | no | Optional extra person fields to return, e.g. gender, birthday, anniversary, school_grade, marital_status, development_child, special_needs_child, security_code, receipt_name, giving_number, mailing_ad |
Find people matching field values, e.g. {"email":"john@example.com"} or {"lastname":"Smith","volunteer":"yes"}. Searchable keys: firstname, preferred_name, lastname, email, phone, mobile, category_id, archived, contact, deceased, volunteer, gender, birthday, anniversary, marital_status, school_grade, security_code, receipt_name, giving_number, groups, date_added / date_modified / last_login (UTC,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | object | yes | Field → value pairs to match. |
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| fields | array | no | Optional extra person fields to return, e.g. gender, birthday, anniversary, school_grade, marital_status, development_child, special_needs_child, security_code, receipt_name, giving_number, mailing_ad |
Fetch one person by id, optionally with extra fields (birthday, addresses, departments, locations, family, custom fields...). Elvanto: people/getInfo.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The person's id. |
| fields | array | no | Optional extra person fields to return, e.g. gender, birthday, anniversary, school_grade, marital_status, development_child, special_needs_child, security_code, receipt_name, giving_number, mailing_ad |
List the people categories (e.g. New People, Church Members, Inactive) with their ids. Elvanto: people/categories/getAll.
No parameter schema on file.
List the church's custom person fields (id, name, type and allowed values). Use the id as custom_<id> in fields / search. Elvanto: people/customFields/getAll.
No parameter schema on file.
List small groups / ministries with meeting day, time, place and frequency; add fields=["people"] to include members and leaders. Elvanto: groups/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| category_id | no | Only groups in this group category id (or any of these ids). | |
| suspended | string | no | yes = only suspended groups, no = exclude them. Default all. |
| fields | array | no | Optional extra group fields: people (members and their position), categories, departments, demographics, locations. |
Fetch one group by id, optionally with its members (fields=["people"]). Elvanto: groups/getInfo.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The group's id. |
| fields | array | no | Optional extra group fields: people (members and their position), categories, departments, demographics, locations. |
List services (upcoming by default). Add fields such as volunteers (the roster), plans (order of service) and songs to answer 'who is serving Sunday?' or 'what are we singing?'. Elvanto: services/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| start | string | no | Only services on/after this date (yyyy-mm-dd). |
| end | string | no | Only services on/before this date (yyyy-mm-dd). |
| all | string | no | yes = include past services too. Ignored when start/end are given. |
| status | string | no | Only published or only draft services. Default both. |
| service_types | no | Only these service type id(s). | |
| fields | array | no | Optional extra service fields: series_name, service_times, rehearsal_times, other_times, plans (the order of service), volunteers (the roster: who is serving in which position, and whether confirmed), |
Fetch one service by id with optional detail: service/rehearsal times, plan (order of service), volunteers roster, songs, files, notes. Elvanto: services/getInfo.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The service's id. |
| fields | array | no | Optional extra service fields: series_name, service_times, rehearsal_times, other_times, plans (the order of service), volunteers (the roster: who is serving in which position, and whether confirmed), |
List or search the song library by title, artist or lyrics (with CCLI number, categories and locations). Elvanto: songs/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| title | string | no | Only songs whose title matches. |
| artist | string | no | Only songs by this artist. |
| lyrics | string | no | Only songs whose lyrics contain this text. |
| files | boolean | no | Also return attached files. |
List the arrangements of one song — sequence, BPM, keys, lyrics and chord chart (optionally transposed). Elvanto: songs/arrangements/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| song_id | string | yes | The song's id (from elvanto_list_songs). |
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| chord_chart_key | string | no | Transpose the chord chart into this key, e.g. F#. |
| files | boolean | no | Also return attached files. |
List the church's calendars with their ids. Elvanto: calendar/getAll.
No parameter schema on file.
List calendar events between two dates, optionally for specific calendars (use "services" as a calendar to include services). Elvanto: calendar/events/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | Start date (yyyy-mm-dd). |
| end | string | yes | End date (yyyy-mm-dd). |
| calendar | no | Calendar id(s) to read from; "services" for services. | |
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| fields | array | no | Optional extra event fields, e.g. ["locations"]. |
List people flows — the church's follow-up pipelines (e.g. First Time Guest Follow Up) — with their steps and admins. Elvanto: peopleFlows/getAll.
No parameter schema on file.
List the steps of one people flow with descriptions, instructions, due rules and admins. Elvanto: peopleFlows/steps/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flow_id | string | yes | The people flow's id. |
List the people currently in one people-flow step, with status, due date and assigned admin — e.g. who still needs a follow-up call. Not paginated. Elvanto: peopleFlows/steps/people.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_id | string | yes | The people flow step's id. |
| status | string | no | Only people with this status in the step. |
| assigned | string | no | Only people assigned to this admin (person id), or "unassigned". |
List giving / chart-of-accounts categories (funds) with ids; status 1 = active, 0 = archived. Elvanto: financial/categories/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
List giving transactions between two dates, optionally for one fund — donor, date, method, batch and per-fund amounts. Read-only: this server never writes financial records. Elvanto: financial/transactions/getAll.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | Start date (yyyy-mm-dd). |
| end | string | yes | End date (yyyy-mm-dd). |
| category_id | string | no | Only this financial category (fund) id. |
| page | integer | no | Results page to retrieve (1-based). Default 1. |
| page_size | integer | no | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
Add a new person to the church database (e.g. a first-time guest). Returns the new person id and family id. Does not create a login. Elvanto: people/create.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| firstname | string | yes | First name. |
| lastname | string | yes | Last name. |
| preferred_name | string | no | Preferred name (nickname). |
| string | no | Email address. | |
| phone | string | no | Phone number (non-digits are stripped by Elvanto). |
| mobile | string | no | Mobile number (non-digits are stripped by Elvanto). |
| category_id | string | no | People category id (see elvanto_list_people_categories). |
| archived | string | no | Mark the person archived (yes) or not (no). |
| contact | string | no | Mark the person a contact (yes) or not (no). |
| volunteer | string | no | Mark the person a volunteer (yes) or not (no). |
| family_id | no | Family id to join an existing family, or "new" to start a new family. | |
| family_relationship | string | no | Relationship within the family. |
| fields | object | no | Extra fields to set, e.g. {"gender":"Male","birthday":"1989-04-23","marital_status":"Married","departments":["Music"],"custom_<field id>":"value"}. Use *_replace / *_remove variants (e.g. departments_ |
Edit an existing person's details — name, contact info, category, flags, family, or extra fields. Only the fields you pass change. Cannot touch username, password or login status. Elvanto: people/edit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The person's id. |
| firstname | string | no | First name. |
| lastname | string | no | Last name. |
| preferred_name | string | no | Preferred name (nickname). |
| string | no | Email address. | |
| phone | string | no | Phone number (non-digits are stripped by Elvanto). |
| mobile | string | no | Mobile number (non-digits are stripped by Elvanto). |
| category_id | string | no | People category id (see elvanto_list_people_categories). |
| archived | string | no | Mark the person archived (yes) or not (no). |
| contact | string | no | Mark the person a contact (yes) or not (no). |
| volunteer | string | no | Mark the person a volunteer (yes) or not (no). |
| family_id | no | Family id to join an existing family, or "new" to start a new family. | |
| family_relationship | string | no | Relationship within the family. |
| fields | object | no | Extra fields to set, e.g. {"gender":"Male","birthday":"1989-04-23","marital_status":"Married","departments":["Music"],"custom_<field id>":"value"}. Use *_replace / *_remove variants (e.g. departments_ |
Add a person to a group, optionally as Leader or Assistant Leader. Undoable by removing them from the group in Elvanto. Elvanto: groups/addPerson.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_id | string | yes | The group's id. |
| person_id | string | yes | The person's id. |
| position | string | no | Position in the group. Omit for a regular member. |
Put a person into a people-flow step (e.g. start a new guest's follow-up), optionally assigning a step admin. Elvanto: peopleFlows/steps/addPerson.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_id | string | yes | The people flow step's id. |
| person_id | string | yes | The person's id. |
| assign_to | string | no | Person id of the step admin to assign them to. |
Create an event on a calendar, optionally repeating. Times are 24-hour GMT. Use status "draft" to stage it unpublished. Elvanto: calendar/events/create.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Event name. |
| calendar_id | string | yes | Calendar id (see elvanto_list_calendars). |
| start | string | yes | Start, yyyy-mm-dd hh:mm:ss (24h, GMT). |
| end | string | yes | End, yyyy-mm-dd hh:mm:ss (24h, GMT). |
| organizer | string | yes | Person id of the organizer. |
| status | string | no | Visibility. Default public. |
| all_day | string | no | All-day event? Default no. |
| where | string | no | Where the event is held. |
| description | string | no | Description (basic HTML allowed). |
| color | string | no | Hex color, e.g. #FF0000. |
| register_url | string | no | Registration website URL. |
| who_can_attend | string | no | "all" to let anyone attend; omit for invite-only. |
| show_guest_list | string | no | Show the guest list on the event page? Default no. |
| repeat | string | no | Make it a repeating event. |
| repeat_frequency | integer | no | How often to repeat. Required for daily, monthly, yearly. |
| repeat_on | string | no | Weekly/fortnightly: monday..sunday. Monthly: weekday or monthday. |
| repeat_occurrences | integer | no | Number of repeats. |
| repeat_end_date | string | no | Stop repeating at, yyyy-mm-dd hh:mm:ss (GMT). |
| locations | no | Location(s) to add to the event. |
Free
$0 forever
- 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 Elvanto or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Elvanto can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.