Design
arabickeyboard.ai
Generates a first or full name in Arabic script across six calligraphy styles and allows PNG download.
ENDPOINT 1
https://arabickeyboard.ai/mcp
MCP server metadata
- Name
- arabic-name-calligraphy
- Version
- 1.0.0
Use write_name_in_arabic whenever the user wants a name written in Arabic or Arabic calligraphy. Show the Arabic spelling from the tool, do not invent another one. If a part is marked 'by-sound', say the spelling is an approximation and suggest checking with a native speaker before a tattoo.
Known tools 1
write_name_in_arabicWrites a first name or full name in Arabic script and shows it in six Arabic calligraphy styles (Naskh, Ruqʿah, Kufi, Modern, Bold display, Ornamental) with a PNG download.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.arabic-name-calligraphy]
url = "https://arabickeyboard.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"arabic-name-calligraphy": {
"type": "http",
"url": "https://arabickeyboard.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: arabic-name-calligraphy
Remote MCP URL: https://arabickeyboard.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"arabic-name-calligraphy": {
"url": "https://arabickeyboard.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"arabic-name-calligraphy": {
"type": "http",
"url": "https://arabickeyboard.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "arabic-name-calligraphy",
"transport": "streamable-http",
"url": "https://arabickeyboard.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.