Hellō Admin▌
by hellocoop
Manage and secure Hellō authentication apps with Hellō Admin — create, configure, and monitor user authentication quickl
Create and manage Hellō authentication applications
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Developers building apps with Hellō authentication
- / Managing multiple Hellō applications from AI assistants
- / Automating authentication app setup and configuration
capabilities
- / Create new Hellō authentication applications
- / Update existing application settings
- / Generate and manage application secrets
- / Upload application logos
- / Read application configurations
- / Access developer profile and team context
what it does
Manages Hellō authentication applications through an MCP server. Lets you create, update, and configure Hellō apps directly from your AI assistant.
about
Hellō Admin is an official MCP server published by hellocoop that provides AI assistants with tools and capabilities via the Model Context Protocol. Manage and secure Hellō authentication apps with Hellō Admin — create, configure, and monitor user authentication quickl It is categorized under developer tools. This server exposes 1 tool that AI clients can invoke during conversations and coding sessions.
how to install
You can install Hellō Admin in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
license
MIT
Hellō Admin is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
@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
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
- Actions:
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 tohello.coop)HELLO_ADMIN: Override the admin server URL (defaults tohttps://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
FAQ
- What is the Hellō Admin MCP server?
- Hellō Admin is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Hellō Admin?
- This profile displays 33 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.8 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.8★★★★★33 reviews- ★★★★★Chaitanya Patil· Dec 16, 2024
We evaluated Hellō Admin against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Benjamin Perez· Dec 8, 2024
I recommend Hellō Admin for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Ishan Sanchez· Dec 8, 2024
Hellō Admin is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Benjamin Chawla· Nov 27, 2024
Hellō Admin reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ishan Okafor· Nov 27, 2024
According to our notes, Hellō Admin benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Piyush G· Nov 7, 2024
Hellō Admin has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Shikha Mishra· Oct 26, 2024
According to our notes, Hellō Admin benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Ishan Ramirez· Oct 18, 2024
Useful MCP listing: Hellō Admin is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Benjamin Sanchez· Oct 18, 2024
Hellō Admin has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Sakura Huang· Sep 25, 2024
According to our notes, Hellō Admin benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 33