Skip to main content
Glama
hellocoop

Hellō Admin MCP Server

Official
by hellocoop

@hellocoop/admin-mcp (BETA)

Model Context Protocol (MCP) server for creating and managing Hellō applications.

🚧 BETA Status: This MCP server is currently in beta. We're actively seeking feedback and welcome contributions! Please report issues, suggest improvements, or submit pull requests to help us improve the developer experience.

Quick Install

📖 Full Documentation & Installation Guide

Quick Configuration

Copy one of these configurations into your MCP client settings:

NPM Package (Latest):

{
  "hello-admin-stdio": {
    "command": "npx",
            "args": ["-y", "@hellocoop/admin-mcp@latest"],
    "type": "stdio"
  }
}

HTTP Transport (Remote):

{
  "hello-admin-http": {
          "url": "https://admin-mcp.hello.coop/",
    "type": "http"
  }
}

📖 See Local Development Setup for running from source

Related MCP server: AppsAI MCP Server

Usage

This MCP server provides a single powerful tool (hello_manage_app) that lets you create and manage your Hellō applications directly from your AI assistant. Unlike traditional APIs, every operation automatically includes your complete developer context - profile, teams, and applications - making it perfect for AI assistants.

📖 For detailed usage instructions, examples, and troubleshooting, visit: hello.dev/docs/admin-mcp

Features

  • 🏢 Context-Aware Operations: Every tool call automatically includes your current developer profile, teams, and applications for seamless context

  • 📱 Unified Application Management: Single powerful tool for all app operations (create, read, update, secrets, logos)

  • 🔐 Secure OAuth Integration: Browser-based authentication with JWT token validation

  • 🌐 Multi-Transport Support: Works with both stdio (local) and HTTP (remote) MCP transports

  • 📊 Built-in Analytics: Usage tracking and performance monitoring for optimization

  • 🎨 Logo Management: Upload logos with automatic light/dark theme support

  • ⚙️ Environment Flexibility: Configurable domains and admin servers

Available Tools

🎯 Core Tool:

  • hello_manage_app - The main tool for all application management

    • Actions: create, read, update, create_secret, update_logo_from_data, update_logo_from_url

    • Always includes: Your current profile, teams, and applications in every response

    • Auto-context: Automatically uses your default team if none specified

    • Smart defaults: Generates app names from your profile if not provided

Key Benefits

🔄 Always In Context: Unlike traditional APIs, every tool response includes your complete developer context:

  • Your user profile (name, email, picture)

  • All your teams/organizations with roles

  • All your applications with team associations

  • Current team and application state

This means you never lose context between operations - perfect for AI assistants that need to understand your complete development environment.

Tool Actions & Response Structure

hello_manage_app Actions:

📝 create - Create new applications

  • Auto-generates team if none exists

  • Creates smart default names from your profile

  • Returns: { profile, application, action_result }

👁️ read - Read application details

  • Without client_id: Returns your complete profile context

  • With client_id: Returns profile + specific application

  • Returns: { profile, application?, action_result }

✏️ update - Update application settings

  • Modify any application property

  • Returns: { profile, application, action_result }

🔑 create_secret - Generate client secrets

  • Creates secure OAuth client secrets

  • Returns: { profile, application, client_secret, action_result }

🎨 update_logo_from_data - Upload logo from base64 data

  • Supports light/dark themes

  • Auto-updates application with logo URL

  • Returns: { profile, application, update_result, action_result }

🔗 update_logo_from_url - Upload logo from URL

  • Fetches and uploads from provided URL

  • Supports light/dark themes

  • Returns: { profile, application, update_result, action_result }

Every response includes your complete profile context, making it perfect for AI assistants that need to maintain awareness of your development environment.

Available Resources

  • Hellō Documentation - Complete integration documentation

  • Hellō Quickstarts - Framework-specific setup guides

  • Hellō Buttons - Login button implementation guide

  • Hellō Scopes - Available scopes and claims reference

  • Hellō Wallet API - Wallet API reference documentation

  • Hellō Logo Design Guidance - Comprehensive guide for creating theme-appropriate logos

Environment Variables

  • HELLO_DOMAIN: Override the default domain (defaults to hello.coop)

  • HELLO_ADMIN: Override the admin server URL (defaults to https://admin.hello.coop)

Contributing & Development

We want your feedback! This MCP server is in beta and we're actively improving it based on real-world usage.

How to Contribute

  • 🐛 Report Issues: GitHub Issues - Found a bug or have a feature request?

  • 🔧 Submit Pull Requests: GitHub PRs - Help us improve the server

  • 💬 Join the Discussion: Discord - Share feedback and get help

Local Development

For local development and testing:

# Clone the repository
git clone https://github.com/hellocoop/admin-mcp
cd admin-mcp

# Install dependencies
npm install

The configure your AI client to run the local version

Local Development (Node.js):

{
  "hello-admin-local": {
    "command": "node",
            "args": ["path/to/HelloCoop/admin-mcp/src/stdio.js"],
    "type": "stdio"
  }
}

Testing

Run the comprehensive test suite:

# Run all automated tests
npm test

Available Tools

1 tool
hello_manage_appB

Manage Hellō applications - create, read, update, create secrets, and upload logos

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoName of the application (optional for: create, update - if not provided for create, will be generated from user name)
themeNoLogo theme - whether this is for light or dark mode (optional for: update_logo_from_data, update_logo_from_url, defaults to "light")
actionYesAction to perform: create (new app), read (get app), update (modify app), create_secret (generate secret), update_logo_from_data (set logo from base64 data), update_logo_from_url (set logo from URL)
pp_uriNoPrivacy Policy URI (optional for: create, update)
team_idNoID of the team that owns the application (optional for all actions - uses default team if not specified)
tos_uriNoTerms of Service URI (optional for: create, update)
logo_urlNoURL of the logo image to fetch and set (required for: update_logo_from_url)
client_idNoID of the OAuth client/application (optional for read - returns profile if omitted; required for: update, create_secret, update_logo_from_data, update_logo_from_url)
logo_dataNoBase64 encoded logo data (required for: update_logo_from_data)
device_codeNoWhether the application supports device code flow (optional for: create, update)
dev_wildcardNoAllow wildcard domain redirects in development environment (optional for: create, update)
dev_127_0_0_1NoAllow 127.0.0.1 redirects in development environment (optional for: create, update)
dev_localhostNoAllow localhost redirects in development environment (optional for: create, update)
dev_redirect_urisNoArray of allowed redirect URIs for development environment (optional for: create, update)
logo_content_typeNoMIME type of the logo data, e.g. "image/png" (required for: update_logo_from_data; auto-detected for: update_logo_from_url)
prod_redirect_urisNoArray of allowed redirect URIs for production environment (optional for: create, update)

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. However, it only lists action names without describing side effects, idempotency, authentication requirements, or error conditions. The actions imply mutation for create/update/create_secret/logo actions and idempotency for read, but this is not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that lists the core actions. It is front-loaded with the primary verb 'Manage' and the resource. While efficient, a slightly more structured format could improve readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 16 parameters and no output schema, the description provides a high-level summary but lacks details on required fields per action, error handling, and return values. It is minimally adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no parameter information beyond what is in the schema, thus baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies the resource 'Hellō applications' and lists distinct actions: create, read, update, create secrets, and upload logos. This clearly defines the tool's scope and purpose, and as there are no sibling tools, differentiation is not needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide guidance on when to use this tool versus alternatives, nor does it help choose between the multiple actions. While action names are self-explanatory, explicit usage context is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.6.1
    • First observedhello_manage_app

TDQS

A3.5/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools. The tool's bundled operations are all focused on application management, ensuring clear distinction from non-existent alternatives.

Naming Consistency5/5

With a single tool, naming is trivially consistent. The name 'hello_manage_app' follows a clear verb_noun pattern with underscores, which is a reasonable convention.

Tool Count2/5

A single tool attempting to cover all management operations (CRUD, secrets, logos) for Hellō applications is too few. Typically, separate tools for each operation (e.g., create, read, update, delete) would provide better granularity and clarity.

Completeness3/5

The tool covers create, read, update, secrets, and logos, but lacks an explicit delete operation and potentially the ability to list all applications. This leaves notable gaps in the lifecycle, though core functionality is present.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to directly manage Beyond Identity resources such as identities, groups, applications, SSO configurations, and credentials via natural language tool calls.
    16
    Apache 2.0
  • A
    license
    Not graded
    quality
    F
    maintenance
    Enables AI agents to manage App Store Connect apps, including registering bundle IDs, uploading metadata and screenshots, setting age ratings, managing TestFlight groups and testers, and submitting apps for review.
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hellocoop/admin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server