classify_text_custom — Brainiall NLP MCP Tool
classify_text_custom
(classify text custom) is one of 22 tools on the
Brainiall NLP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call classify_text_custom from your client
- Claude Code Brainiall NLP classify_text_custom run in your project directory
- Claude Desktop Brainiall NLP classify_text_custom ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Brainiall NLP classify_text_custom ~/.cursor/mcp.json
- VS Code Brainiall NLP classify_text_custom .vscode/mcp.json
- Zed Brainiall NLP classify_text_custom ~/.config/zed/settings.json
- Windsurf Brainiall NLP classify_text_custom ~/.codeium/windsurf/mcp_config.json
- Cline Brainiall NLP classify_text_custom ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Brainiall NLP classify_text_custom ~/.gemini/settings.json
- Grok Brainiall NLP classify_text_custom .mcp.json (in your project root)
- ChatGPT Brainiall NLP classify_text_custom Settings → Connectors → Advanced → Developer mode
- Claude.ai Brainiall NLP classify_text_custom Settings → Connectors → Add custom connector
- LangChain Brainiall NLP classify_text_custom pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nlp https://api.brainiall.com/mcp/nlp/mcpOther tools on this server
- analyze_toxicity
- analyze_sentiment
- extract_entities
- detect_pii
- detect_language
- check_nlp_service
- translate_text
- summarize_text
- answer_question
- knowledge_ingest
- knowledge_query
- knowledge_list_documents
- fraud_score
- fraud_feedback
- extract_key_phrases
- aspect_sentiment
- link_entities_to_wikidata
- detect_conversational_pii
- detect_prompt_injection
- check_groundedness
- detect_protected_material
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.