# Humaify agent and developer resources

AI consulting, custom development, AI workshops and managed phone assistants: find Humaify's public resources and MCP connection here.

## When to use Humaify

For businesses that want to assess AI use cases, define an initial pilot, automate repetitive workflows or train their team to use AI with human review. Humaify AI workshops serve leaders and employees and use tasks from their own organisation.

- [Services](/leistungen)

- [AI workshops](/workshops)

## MCP: read public information

Connect your MCP client over Streamable HTTP to /mcp on this website. No API key is required for public information. Tools are list_services, get_workshop_information and get_contact_information; language selects de or en. Resources humaify://website/de and humaify://website/en provide the Markdown homepage.

The endpoint supports MCP revision 2026-07-28 and stateless compatibility with older clients' initialize handshake. It reads published information and does not book workshops, submit enquiries, place calls or access customer systems.

- [MCP server description](/server.json)

- [Technical Markdown guide](/developers.md)

## Discuss a project

An agent can summarise the task, current workflow, desired outcome and existing systems for a conversation. It must obtain explicit user permission before sending a message or submitting the form. Form enquiries reach the team only after email confirmation. Scope, prices and availability are agreed with Humaify.

- [Contact Humaify](/contact)

## Further resources

Humaify provides AI services. Railway hosts this staging website; Railway's developer documentation and third-party Railway MCP servers are separate from Humaify. This site does not offer a general REST API, booking API or Humaify SDK.

- [llms.txt](/llms.txt)

- [Markdown homepage](/index.md)

- [About Humaify](/about)

- [Privacy](/privacy)

## Connection details

POST /mcp with Content-Type: application/json and Accept: application/json, text/event-stream. Use the official MCP client SDK for protocol negotiation. The endpoint accepts the current 2026-07-28 envelope and stateless 2025-era initialize requests. GET and DELETE return 405 because no persistent session or independent event stream is offered.

Public read-only tools require no authentication. Tool inputs contain language (de or en, default de) for list_services and get_workshop_information; get_contact_information takes an empty object. There are no tools for sending messages, payments, bookings or private data.

The server.json file uses the official MCP Registry schema. The /.well-known/mcp URL is an informational copy, not a separate protocol or a claim of registry registration. Its remotes entry gives the HTTPS endpoint for this deployment.