Ashby MCP Server

Instructions

Implementation Reference

• src/ashby/server.py:407-434 (handler)

  The handler function that processes tool calls by mapping the tool name to an Ashby API endpoint and executing the request.

  @server.call_tool()
  async def handle_call_tool(name: str, arguments: dict[str, Any]) -> list[types.TextContent]:
      """Route tool calls to the correct Ashby endpoint, passing arguments directly."""
      endpoint = TOOL_ENDPOINT_MAP.get(name)
      if not endpoint:
          return [types.TextContent(type="text", text=f"Unknown tool: {name}")]
  
      try:
          # Pass arguments straight through -- tool schemas already use Ashby's
          # camelCase param names so no translation is needed.
          response = ashby.post(endpoint, data=arguments if arguments else None)
          return [types.TextContent(type="text", text=json.dumps(response, indent=2))]
      except requests.exceptions.HTTPError as e:
          error_body = ""
          if e.response is not None:
              try:
                  error_body = e.response.text
              except Exception:
                  pass
          return [
              types.TextContent(
                  type="text",
                  text=f"Ashby API error on {endpoint}: {e}\n{error_body}",
              )
          ]
      except Exception as e:
          return [types.TextContent(type="text", text=f"Error calling {endpoint}: {e}")]

• src/ashby/server.py:134-144 (schema)

  Tool definition and schema for candidate_info.

  types.Tool(
      name="candidate_info",
      description="Get full details of a single candidate by ID.",
      inputSchema={
          "type": "object",
          "properties": {
              "id": {"type": "string", "description": "The candidate ID (UUID)"},
          },
          "required": ["id"],
      },
  ),

• src/ashby/server.py:380-380 (registration)

  Mapping registration for candidate_info tool to the /candidate.info API endpoint.

  "candidate_info": "/candidate.info",