Skip to main content
Glama
MSPbotsAI

simpleinout-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AUTH_MODENo`gateway` = credentials per-request via headers; `env` = shared credentials from env vars (local dev only)gateway
MCP_HTTP_PORTNoHTTP server port8080
MCP_TRANSPORTNo`stdio` (Claude Desktop) or `http` (gateway)stdio
SIMPLEINOUT_CLIENT_IDYesSimple In/Out OAuth2 client ID
SIMPLEINOUT_CLIENT_SECRETYesSimple In/Out OAuth2 client secret
SIMPLEINOUT_REFRESH_TOKENYesRefresh token obtained from the one-time interactive authorization

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
simpleinout_get_current_companyA

Retrieve the current company.

    API: GET /companies/my

    Args:
        expand: Optional comma-separated list of related resources to embed.
simpleinout_list_statusesA

List status-change history across the whole company within a date range.

    API: GET /statuses

    Args:
        created_at: Required. Date/time range filter, e.g. "1523854800..1524459599"
            (epoch seconds, `..` between two values for a range).
simpleinout_list_my_statusesA

List the current authenticated user's status history within a date range.

    API: GET /users/my/statuses

    Args:
        created_at: Required. Date/time range filter, e.g. "1523854800..1524459599".
simpleinout_list_user_statusesA

List a specific user's status history within a date range.

    API: GET /users/:id/statuses

    Args:
        user_id: Required. The user's ID.
        created_at: Required. Date/time range filter, e.g. "1523854800..1524459599".
simpleinout_create_my_statusA

Create (change) the current authenticated user's status — the core check-in/check-out action.

    API: POST /users/my/statuses

    Args:
        status: Required. One of "in", "remote", "busy", "break", "out",
            "sick", "vacation".
        comment: Optional comment to attach to the status change.
        created_at: Optional timestamp to backdate/schedule the status change.
simpleinout_create_user_statusA

Create (change) another user's status on their behalf. Requires the acting account to have permission to manage that user's status.

    API: POST /users/:id/statuses

    Args:
        user_id: Required. The user's ID to change the status for.
        status: Required. One of "in", "remote", "busy", "break", "out",
            "sick", "vacation".
        comment: Optional comment to attach to the status change.
        created_at: Optional timestamp to backdate/schedule the status change.
simpleinout_list_usersA

List all users in the company.

    API: GET /users

    Args:
        name: Filter by name.
        email: Filter by email address.
        group_id: Filter by group ID.
        status: Filter by current status.
simpleinout_get_userA

Retrieve a specific user.

    API: GET /users/:id

    Args:
        user_id: Required. The user's ID.
simpleinout_get_current_userA

Retrieve the current authenticated user.

    API: GET /users/my
simpleinout_list_groupsA

List all groups.

    API: GET /groups

    Args:
        page: Page number.
        page_size: Results per page.
simpleinout_list_beaconsA

List all beacons (Bluetooth presence beacons).

    API: GET /beacons

    Args:
        page: Page number.
        page_size: Results per page.
simpleinout_list_fencesA

List all geofences.

    API: GET /fences

    Args:
        page: Page number.
        page_size: Results per page.
simpleinout_list_networksA

List all Wi-Fi networks used for automatic presence detection.

    API: GET /networks

    Args:
        page: Page number.
        page_size: Results per page.
simpleinout_list_announcementsA

List all announcements for the company.

    API: GET /announcements

    Args:
        page: Page number.
        page_size: Results per page.
        expand: Optional comma-separated list of related resources to embed.
simpleinout_list_rolesA

List all roles defined in the company (needed to create a user, which requires a role_id).

    API: GET /roles

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 15 tools

Disambiguation4/5

Most tools target distinct resources (roles, users, groups, announcements, beacons, etc.), and the three status-listing tools are differentiated by scope (company, self, specific user). The only potential confusion is between list_my_statuses and list_user_statuses, but descriptions clearly indicate self vs. other.

Naming Consistency5/5

All tools follow a consistent `simpleinout_` prefix with a clear verb_noun pattern (list_*, get_*, create_*). No mixed conventions or ambiguous verbs; the naming is uniform and predictable.

Tool Count4/5

15 tools is within a reasonable range for a presence/status management server. A few list-only tools (beacons, fences, networks) feel slightly peripheral, but they align with the presence detection domain and do not make the set unwieldy.

Completeness3/5

The core workflow of checking in/out is covered via create_my_status and create_user_status, and status history is queryable. However, there are notable gaps: no create/update/delete for users, roles, groups, announcements, or configuration entities like beacons/fences/networks, limiting full lifecycle management.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources