Skip to Content

n8n and custom code

Any MCP client that speaks Streamable HTTP and can send a header works.

  • URL: https://mcp.appneck.com/
  • Header: Authorization: Bearer anmcp_o_…

n8n

In an MCP Client Tool node, set the endpoint to https://mcp.appneck.com/, transport HTTP Streamable, and authentication Bearer, with your token as the credential.

A quick check with curl

curl -s https://mcp.appneck.com/ \ -H "Authorization: Bearer $APPNECK_MCP_TOKEN" \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

A JSON result with "protocolVersion" means the token works. A 401 means it is wrong, expired or revoked.

SDKs

With the official MCP SDKs, use the Streamable HTTP client transport and pass the header in its request options. The server is stateless: no session id to keep.