How to Use the MIT DBLP MCP in CrewAI

Q: How do I assign MIT DBLP tools to specific agents in CrewAI?

You pass the server URL in the mcps array of the specific CrewAI Agent definition. For instance, give your systems researcher agent access to searchsystemspapers while keeping other tools hidden.

Q: Can a CrewAI agent recursively crawl MIT DBLP co-author networks?

Yes, by using getcoauthors in a loop, though you must configure the agent's max iterations. Otherwise, the crew might trigger rate limits by crawling too deep into the collaboration graph.

Q: Do I need to install separate Python packages for these tools?

No, you only need crewai and crewaitools. The framework connects directly to the managed Vinkius endpoint, exposing all 16 search and retrieval tools out of the box.

Deploy a team of autonomous research agents using CrewAI and the MIT DBLP MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect MIT DBLP MCP to CrewAI

Create your Vinkius account to connect MIT DBLP to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup MIT DBLP with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run collaborative literature reviews in CrewAI

`search_publications` allows your CrewAI research crew to divide and conquer massive academic databases. One agent searches for relevant DBLP papers while a separate analyst agent digests the results to find trends. By sharing context across the crew, agents can use `get_publication` via the MCP server to fetch full metadata for specific papers flagged by other team members. It mirrors how a human research lab actually operates.

Automate expert profiling with multi-agent crews

`get_author_stats` provides your profiling agent with immediate metrics on researcher output and DBLP citation history. Meanwhile, a co-authorship agent runs `get_coauthors` to map out the researcher's professional network. Your crew compiles these data points into a single, clean text file. Bottom line: because these agents share memory, they avoid redundant DBLP API calls and build an accurate map of academic influence without getting blocked.

Track conference trends autonomously

`search_venues` gives your tracking agent the ability to locate specific conferences and journals. A coordinator agent then assigns the task of pulling recent papers to a data-gathering agent using `get_venue_publications`. This multi-agent setup can monitor multiple venues simultaneously. Your crew outputs structured summaries of what's hot in systems, theory, or AI without any human intervention.

Setup guide

Set up MIT DBLP MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke MIT DBLP tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="MIT DBLP Analyst",
    goal="Access and analyze MIT DBLP data via MCP.",
    backstory="Expert analyst with direct MIT DBLP access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent MIT DBLP transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="MIT DBLP Analyst",
        goal="Access and analyze MIT DBLP data via MCP.",
        backstory="Expert analyst with direct MIT DBLP access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent MIT DBLP transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DBLP. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect MIT DBLP now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about MIT DBLP MCP in CrewAI

You pass the server URL in the `mcps` array of the specific CrewAI Agent definition. For instance, give your systems researcher agent access to `search_systems_papers` while keeping other tools hidden.

Yes, by using `get_coauthors` in a loop, though you must configure the agent's max iterations. Otherwise, the crew might trigger rate limits by crawling too deep into the collaboration graph.

The framework relies on the server's HTTP transport layer to bubble up rate limit errors. You should configure your agents with backoff parameters to prevent them from hitting the upstream API too aggressively.

No, you only need `crewai` and `crewai[tools]`. The framework connects directly to the managed Vinkius endpoint, exposing all 16 search and retrieval tools out of the box.

No, the MCP server only handles public academic metadata, author names, and venue keys. All tool execution happens in an ephemeral, zero-trust sandbox that isolates your crew's internal reasoning from the public API.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript