How do I use @danijeun/fanar-mcp-server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@danijeun/fanar-mcp-server Translate 'good morning' to Arabic" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

@danijeun/fanar-mcp-server

by danijeun

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Fanar MCP Tools

A Model Context Protocol (MCP) server for Fanar API tools: Islamic RAG, image generation, and translation. Publishable as an npm package and usable as a CLI tool or MCP server.

Installation

npm install -g @danijeun/fanar-mcp-server

Or use with npx:

npx @danijeun/fanar-mcp-server

Related MCP server: MCP AI Chat LangChain

Environment Variable

Set your Fanar API key:

export FANAR_API_KEY=your_api_key_here

Usage (CLI)

You can run the MCP server directly:

@danijeun/fanar-mcp-server

Or via npx:

npx @danijeun/fanar-mcp-server

Usage (MCP Client)

Configure your MCP client to use this server. Example config:

{
  "mcpServers": {
    "fanar_mcp": {
      "command": "npx",
      "args": ["@danijeun/fanar-mcp-server"],
      "env": {
        "FANAR_API_KEY": "your api key here"
      }
    }
  }
}

Tools

fanar_rag

Input: { messages: [{ role: string, content: string }], model?: string }
Output: { content: [{ type: "text", text: string }], references?: any[] }

fanar_image_gen

Input: { prompt: string }
Output: { content: [{ type: "image", image: string }] } (base64)

fanar_translate

Input: { text: string, langpair: string, preprocessing?: string }
Output: { content: [{ type: "text", text: string }] }

License

None

Available Tools

3 tools

fanar_image_genD

ParametersJSON Schema

Name	Required	Description	Default
`prompt`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fanar_ragD

ParametersJSON Schema

Name	Required	Description	Default
`messages`	Yes
`model`	No		Islamic-RAG

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fanar_translateD

ParametersJSON Schema

Name	Required	Description	Default
`text`	Yes
`langpair`	Yes
`preprocessing`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesv1.1.0May 25, 2026
- First observedfanar_image_gen
- First observedfanar_rag
- First observedfanar_translate

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2/5.0

Scored 2026-05-25 23:25 across 3 tools

Disambiguation4/5

Tool names suggest distinct functionalities (image generation, RAG, translation), but missing descriptions could cause minor confusion about exact purpose or scope.

Naming Consistency5/5

All tools follow a consistent 'fanar_verb_noun' pattern using snake_case, making the naming predictable and clean.

Tool Count5/5

With only three tools, the server is well-scoped for a focused set of AI capabilities, each tool serving a clear purpose.

Completeness3/5

Without descriptions, it's unclear if the three tools cover the intended domain fully; gaps may exist but are not obvious from names alone.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

mcp COAuth
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
216
Apideck MCP A
dev.apideck.mcp
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Developer Tools
42
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
Sentry AOAuth
dev.sentry.mcp
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Monitoring Developer Tools Observability
3

Related MCP Servers

MCP-PIF Server
Autonomous Agents Knowledge & Memory Developer Tools
hungryrobot1
F
license
Not graded
quality
F
maintenance
This server implements the Model Context Protocol to facilitate meaningful interaction and understanding development between humans and AI through structured tools and progressive interaction patterns.
Updated a year ago (2025-10-20 14:28 UTC)
57
-
MCP AI Chat LangChain
RAG Systems Developer Tools
badrinathvm
F
license
Not graded
quality
D
maintenance
A basic Model Context Protocol server implementation that demonstrates core functionality including tools and resources for AI chat applications.
Updated a year ago (2025-05-20 04:30 UTC)
-
Zulip MCP Server
Communication Developer Tools App Automation
avisekrath
A
license
A
quality
D
maintenance
A Model Context Protocol server that enables AI assistants to interact with Zulip workspaces by exposing REST API capabilities as tools for message operations, channel management, and user interactions.
Updated a year ago (2025-06-21 17:00 UTC)
25
11 npm
8
MIT
AI Agent MCP Server
Developer Tools Autonomous Agents Code Execution
luminosita
F
license
Not graded
quality
D
maintenance
A Model Context Protocol server implementation built with FastAPI that enables AI agent interactions. Provides a structured foundation for building AI-powered applications with proper data validation and modern Python tooling.
Updated 10 months ago (2025-11-19 21:08 UTC)
-