
Neuronsearchlab
com.neuronsearchlabPublished by neuronsearchlab.comOfficial publisherv2.0.0Updated Nov 4, 2026
Recommendations, search, catalogue, analytics, and platform admin tools for NeuronSearchLab
Overview
Neuronsearchlab's hosted MCP server (console.neuronsearchlab.com), published by neuronsearchlab.com; OAuth sign-in or API key required; Streamable HTTP.
No AI overview yet: these facts come from the registry entry and the server itself.
- Publisher
- neuronsearchlab.com
- Endpoint
- console.neuronsearchlab.com
- Documentation
- docs.neuronsearchlab.com
- Last checked
Installation
In SourceWeft
- Open Neuronsearchlab in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.neuronsearchlab%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"neuronsearchlab": {
"type": "http",
"url": "https://console.neuronsearchlab.com/api/mcp"
}
}
}README
@neuronsearchlab/mcp
MCP (Model Context Protocol) server for NeuronSearchLab. Gives any MCP-compatible AI client (Claude, Codex, Cursor, Windsurf, etc.) direct access to NeuronSearchLab recommendations, product/content search, catalogue operations, analytics, and platform controls.
Two ways to run it:
- Hosted (recommended, no install):
https://console.neuronsearchlab.com/api/mcp— Streamable HTTP with OAuth sign-in or an NSL API key. Listed on the MCP Registry ascom.neuronsearchlab/mcp(searchneuronsearchlabin the registry API or directory). - Local stdio via npm:
npx -y @neuronsearchlab/mcpin two modes —public(recommendations, events, catalogue via OAuth client credentials) orinternal(admin platform via console API key).
Connect to the hosted server (no install)
The hosted endpoint runs a submission-safe customer administration profile. It includes first-class tools for plan and usage visibility, ranking configuration, experiments, training, analytics, catalogue inspection, API-key inventory and revocation, integrations, and event types. Every hosted tool declares its OAuth requirement and requires the authenticated team's admin scope. Credential creation, billing mutations, and the arbitrary platform API fallback remain available only to trusted local/internal clients so secrets, purchases, and unbounded API calls are not exposed in ChatGPT. Keys minted through OAuth consent appear in console → Security and can be revoked there anytime.
claude.ai / Claude Desktop — Settings → Connectors → Add custom connector → paste https://console.neuronsearchlab.com/api/mcp → Connect, then sign in to your NeuronSearchLab console and approve the scopes.
Claude Code
OpenAI Codex — in ~/.codex/config.toml:
Cursor / Windsurf / other Streamable HTTP clients
Resources
- Product site: https://www.neuronsearchlab.com
- MCP setup guide: https://docs.neuronsearchlab.com/sdk/mcp
- AI agents for recommendation operations: https://www.neuronsearchlab.com/blog/ai-agents-for-recommendation-operations
- Recommendation systems reading path: https://www.neuronsearchlab.com/blog/recommendation-systems
Tools
API tools
Modes
Public mode
Uses OAuth client credentials and the public API.
Supported:
- recommendations
- events
- catalogue operations
Internal mode
Uses a NeuronSearchLab API key with the admin scope against the console API.
Currently supported:
- account plan and limits:
get_account_planreturns the effective plan, resolved limits, current usage, and exact overages - catalogue search and ranking debug:
search_items,explain_ranking - contexts:
list_contexts,create_context,update_context,delete_context,get_context - rules:
list_rules,create_rule,update_rule,delete_rule,toggle_rule,enable_rule,disable_rule,get_rule - segments:
list_segments,get_segment,create_segment,update_segment,delete_segment - experiments:
list_experiments,get_experiment,create_experiment,update_experiment,start_experiment,stop_experiment,get_experiment_results,refresh_experiment_results - training:
list_training_jobs,get_training_job,create_training_job,cancel_training_job - analytics:
get_ranking_metrics,get_user_analytics,get_item_analytics,compare_items,top_items - event types:
list_event_types,create_event_type,update_event_type,delete_event_type - credentials and integrations:
list_api_keys,revoke_api_key,list_integrations(create_api_keyis local/internal only because it returns credential material) - fallback UI coverage for trusted local/internal clients only:
list_platform_routes,call_platform_api
Quickstart (local stdio)
1. Get credentials
Generate SDK Credentials (OAuth 2.0 client ID + secret) from the NeuronSearchLab console.
2. Add to Claude Desktop
Public mode (recommendations, events, catalogue):
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
Internal mode (admin platform — contexts, rules, analytics, etc.):
Restart Claude Desktop. You'll see a 🔌 neuronsearchlab indicator in the toolbar when it's connected.
Try it: recommendation-ops demo
Once connected, run this named demo path before wiring the server into a larger workflow. It proves that an AI client can operate the recommender as an investigation surface rather than just call a recommendation endpoint.
- List contexts so the assistant confirms the exact surface it is about to inspect.
- Fetch recommendations for a known test user and context.
- Search the catalogue for a concrete product/content phrase and compare the returned item IDs with the recommendation set.
- Explain one ranked item using the
request_idfrom the recommendation or search response when available. - Optional, sandbox only: draft or toggle a rule after the explanation shows the expected leak. Keep production contexts read-only unless the operator explicitly approves a write.
Internal/admin mode can also inspect operational state before making changes:
Next steps after the smoke test:
- create a scoped API key for the client or MCP server
- connect one real recommendation context, such as
homepage-feed - add request attribution to click/view events before judging ranking quality
3. Cursor / other MCP clients
Follow your client's MCP server guide. The command is:
Set NSL_CLIENT_ID + NSL_CLIENT_SECRET for public mode, or NSL_PLATFORM_MODE=internal + NSL_API_KEY for internal mode.
Releases
This repo uses Changesets plus GitHub Actions for automated versioning and npm publishing.
- Add a changeset for any user-facing package change with
npm run changeset - Merge that PR into
main - The
release.ymlworkflow opens or updates a version PR - Merging the version PR publishes
@neuronsearchlab/mcpto npm automatically
To enable trusted publishing, configure the package on npmjs.com to trust the release.yml workflow in this repository.
Configuration
All configuration is via environment variables:
Tool reference
get_recommendations
Fetch personalised recommendations for a user. Returns ranked items with scores and a request_id for attribution.
Inputs
Example
get_recommendation_sets
Fetch every recommendation rail of a page in one request (POST /v1/recommendations/batch). Each set is served and billed on its own and carries its own request_id for attribution; a set that fails reports its own error. Not exposed in the ChatGPT app profile.
Inputs
Example
get_auto_recommendations
Fetch the next auto-generated section for a user's feed. Designed for infinite-scroll — each call returns one curated section (e.g. "Trending this week", "New for you") plus a cursor for the next section. Call until done: true.
Inputs
track_event
Record a user interaction. Always pass request_id from the recommendations response to enable click-through attribution.
Inputs
upsert_item
Add or update an item in the catalogue. The description field is used to generate the embedding — write it to be rich and descriptive.
Inputs
The item ID is generated by NSL and returned in the ingestion response; callers cannot supply it.
patch_item
Partially update an existing catalogue item.
Inputs
delete_items
Permanently remove items. Cannot be undone. To temporarily exclude, use patch_item with active: false.
Inputs
search_items
Search the catalogue by keyword.
Inputs
explain_ranking
Explain why a specific item was ranked at a given position for a user. Returns score breakdown, applied rules, and pipeline trace.
Inputs
list_contexts
List all recommendation contexts (feeds) configured for your team.
Inputs — none
create_context
Create a recommendation context: one rail or surface. A context owns its model and its ranking configuration.
Inputs
Example
get_context
Get one context: its fields, its model, its ranking configuration (template and serving stages) and configuration_enabled (whether serving uses that configuration).
update_context
Update a context. Only the fields you pass change.
Inputs
model is one of:
{ "kind": "automatic" }: the NSL default model.{ "kind": "nsl", "family": "watch_next", "architecture": "gsasrec" }: an NSL model deployed to production.{ "kind": "trained", "id": 41 }: a trained model. It supplies its own candidates, so candidate sources and learned reranking do not apply. Personalized discovery and email digest contexts only.
delete_context
Permanently delete a context, its ranking configuration and its rules.
Inputs
list_rules
List ranking rules, optionally filtered by context_id.
create_rule
Create a ranking rule. Rule types:
Inputs
Example
update_rule / delete_rule / toggle_rule / enable_rule / disable_rule
Update, delete, or enable/disable a rule by rule_id.
get_user_analytics
Get served counts, event breakdown, unique-item activity, and click-through rate for a specific user.
Inputs
get_item_analytics
Get served counts, event breakdown, watch/click counts, and click-through rate for a specific item.
Inputs
compare_items
Compare two items head-to-head by served count, events, clicks, and CTR over the same time window.
Inputs
top_items
List the top items by served count or by matching event activity over a time window. Use metric="served" for generic "top item" or "best performing" questions. Use metric="events" when the user explicitly names an engagement signal (e.g. watch, click, purchase).
Inputs
Example
Authentication
Public mode uses OAuth 2.0 Client Credentials. Tokens are fetched on startup, cached in memory, and auto-refreshed 60 seconds before expiry.
Internal mode uses a NeuronSearchLab API key with the admin scope. Set NSL_API_KEY and NSL_PLATFORM_MODE=internal.
Development
License
MIT
Source: README.md at commit 109b551
Tools
0Version history
4- v2.0.0LatestNov 4, 2026
- v1.3.0Oct 31, 2026
- v1.2.0Sep 23, 2026
- v1.1.0Sep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.