African bank & SWIFT codes, NUBAN resolution, mobile networks, holidays and ISO 4217 currencies.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like Mansa African Financial Reference Data.
https://mansaapi.com/api/mcpAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-heyzod-mansa-african-identity": {
"url": "https://mansaapi.com/api/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Mansa African Financial Reference Data is an MCP server for African bank & SWIFT codes, NUBAN resolution, mobile networks, holidays and ISO 4217 currencies.. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://mansaapi.com/api/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://mansaapi.com/api/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://mansaapi.com/api/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://mansaapi.com/api/mcp.
Mansa African Financial Reference Data uses HTTP transport. Endpoint: https://mansaapi.com/api/mcp.
Mansa African Financial Reference Data inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Mansa African Financial Reference Data does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.