Which integrations are available for this server?

Allows searching and retrieving detailed information about creative projects, user profiles, images, and job listings from Behance.net without requiring an API key.

How do I use Behance MCP Server?

1. Click on "Install 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., "@Behance MCP Server search for UI design projects" 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.

Behance MCP Server

by Arnonfr

Overview Schema Related Servers Score Discussions

TypeScript

Local

🔍 Behance MCP Server

MCP Node.js TypeScript License npm

A powerful Model Context Protocol (MCP) server for scraping Behance.net. Extract projects, user profiles, images, and job listings from Behance's creative community without any API keys or subscriptions.

✨ Features

🔍 Search Projects - Find creative projects by keyword with full metadata (title, creator, stats, fields)
👤 User Profiles - Extract designer and agency profile information
🖼️ Images - Search and collect images from Behance portfolios
💼 Jobs - Get creative job listings with filters (location, category, remote)
📊 Detailed Data - Comprehensive information including descriptions, tools, tags, and media
🔒 No API Key Required - Uses web scraping, no Behance API key needed
💰 Completely Free - No monthly fees or usage limits (unlike Apify's $25/month)

Related MCP server: LinkedIn MCP Server

🚀 Quick Start

Prerequisites

Node.js 18 or higher
npm (comes with Node.js)

Installation

# Clone the repository
git clone https://github.com/Arnonfr/behance-mcp-server.git
cd behance-mcp-server

# Install dependencies
npm install

# Build the TypeScript code
npm run build

Alternative: Install via npx (Coming Soon)

npx behance-mcp-server

⚙️ Configuration

Claude Desktop

Add to your Claude Desktop configuration file:

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%/Claude/claude_desktop_config.json

Linux:

~/.config/Claude/claude_desktop_config.json

Configuration:

{
  "mcpServers": {
    "behance": {
      "command": "node",
      "args": ["/absolute/path/to/behance-mcp-server/dist/index.js"]
    }
  }
}

Cursor

Add to your Cursor MCP settings (Settings → Features → MCP):

{
  "mcpServers": {
    "behance": {
      "command": "node",
      "args": ["/absolute/path/to/behance-mcp-server/dist/index.js"]
    }
  }
}

VS Code / GitHub Copilot

{
  "mcpServers": {
    "behance": {
      "command": "node",
      "args": ["/absolute/path/to/behance-mcp-server/dist/index.js"]
    }
  }
}

Kimi Code CLI

Add to your Kimi MCP configuration (~/.kimi/mcp.json):

{
  "mcpServers": {
    "behance": {
      "command": "node",
      "args": ["/absolute/path/to/behance-mcp-server/dist/index.js"]
    }
  }
}

🛠️ Available Tools

1. `search_behance_projects`

Search for creative projects on Behance.

Parameters:

keyword (string, required): Search term (e.g., "branding", "UI design")
maxItems (number, optional): Maximum results (default: 50, max: 200)

Returns:

Project ID, title, URL
Creator name and profile URL
Thumbnail image
Stats: views, appreciations, comments
Creative fields/categories

Example:

{
  "keyword": "logo design",
  "maxItems": 10
}

2. `get_behance_project_details`

Get detailed information about a specific project.

Parameters:

projectUrl (string, required): Full Behance project URL

Returns:

Full description
All project images
Tags
Tools used

Example:

{
  "projectUrl": "https://www.behance.net/gallery/123456789/Project-Name"
}

3. `search_behance_profiles`

Search for user profiles on Behance.

Parameters:

keyword (string, required): Search term (e.g., "designer", "illustrator")
maxItems (number, optional): Maximum results (default: 50, max: 200)

Returns:

Username and display name
Avatar image
Location
Followers, appreciations, views
Project count
Hiring status

Example:

{
  "keyword": "UI designer London",
  "maxItems": 20
}

4. `get_behance_profile_details`

Get detailed profile information.

Parameters:

profileUrl (string, required): Full Behance profile URL

Returns:

Bio
Company and occupation
Social media links
Complete statistics

Example:

{
  "profileUrl": "https://www.behance.net/username"
}

5. `search_behance_images`

Search for images on Behance.

Parameters:

keyword (string, required): Search term (e.g., "logo", "3d render")
maxItems (number, optional): Maximum results (default: 50, max: 200)

Returns:

Image URLs with dimensions
Associated project info
Creator details

Example:

{
  "keyword": "3d render",
  "maxItems": 30
}

6. `get_behance_jobs`

Get job listings from Behance.

Parameters:

maxItems (number, optional): Maximum results (default: 50, max: 100)
location (string, optional): Filter by location (e.g., "New York", "Remote")
category (string, optional): Filter by category (e.g., "Graphic Design")

Returns:

Job title and company
Location and job type
Posted date
Required skills
Remote availability

Example:

{
  "maxItems": 20,
  "location": "Remote",
  "category": "UI/UX"
}

7. `get_behance_job_details`

Get detailed job listing information.

Parameters:

jobUrl (string, required): Full Behance job URL

Returns:

Full job description
Salary information (if available)

💡 Usage Examples

Search for branding projects:

Search for "branding" projects on Behance, limit to 20 results

Find designers in a location:

Search for UI designer profiles in London

Get job listings:

Get remote graphic design jobs from Behance

Extract project details:

Get full details for project https://www.behance.net/gallery/123456789/Project-Name

🏗️ Development

# Install dependencies
npm install

# Build the project
npm run build

# Watch mode for development
npm run dev

# Run the server
npm start

🧪 Testing

Run the test suite:

npm test

🔧 Troubleshooting

Browser not launching

Make sure you have Chrome/Chromium installed. Puppeteer will download Chromium automatically on first run.

# If Puppeteer fails to download Chromium, try:
PUPPETEER_SKIP_DOWNLOAD=true npm install
npx puppeteer browsers install chrome

Timeout errors

Behance may have rate limiting. Try reducing maxItems or adding delays between requests.

Memory issues

For large scraping operations, consider running with increased Node.js memory:

node --max-old-space-size=4096 dist/index.js

macOS permissions

If you get permission errors on macOS:

# Allow the binary to run
xattr -dr com.apple.quarantine node_modules/puppeteer/.local-chromium/*/chrome-mac/Chromium.app

💰 Pricing Comparison

Feature	Behance MCP Server	Apify Behance Scraper
Monthly Cost	FREE	$25/month + usage
API Key Required	No	Yes
Rate Limits	None (respectful scraping)	Varies
Setup Time	5 minutes	2 minutes
Open Source	✅ Yes	❌ No
Self-hosted	✅ Yes	❌ No

📁 Project Structure

behance-mcp-server/
├── src/
│   ├── index.ts          # MCP server implementation
│   └── scraper.ts        # Behance scraping logic
├── dist/                 # Compiled JavaScript
├── package.json          # Dependencies and scripts
├── tsconfig.json         # TypeScript configuration
├── config-example.json   # Example MCP configuration
├── LICENSE               # MIT License
└── README.md            # This file

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Fork the repository
Create your feature branch (git checkout -b feature/AmazingFeature)
Commit your changes (git commit -m 'Add some AmazingFeature')
Push to the branch (git push origin feature/AmazingFeature)
Open a Pull Request

Development Setup

# Fork and clone
git clone https://github.com/YOUR_USERNAME/behance-mcp-server.git
cd behance-mcp-server

# Install dependencies
npm install

# Create a branch
git checkout -b feature/my-feature

# Make changes and test
npm run build
npm test

# Commit and push
git commit -m "Add my feature"
git push origin feature/my-feature

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

Built with Model Context Protocol
Uses Puppeteer for browser automation
Inspired by the need for free, open-source data extraction tools
Thanks to all contributors!

📧 Support

If you encounter any issues or have questions:

Check the Troubleshooting section
Open an issue on GitHub
Join the discussion in the Discussions tab

🔒 Security

This project uses Puppeteer for web scraping. Please use responsibly and respect Behance's terms of service. The scraper includes rate limiting and respectful crawling practices.

Made with ❤️ for the creative community

If you find this project useful, please ⭐ star the repository!

Available Tools

7 tools

get_behance_job_detailsA

Get detailed information about a specific Behance job listing including full description and salary info.

ParametersJSON Schema

Name	Required	Description	Default
`jobUrl`	Yes	Full URL of the Behance job listing

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only mentions that the tool returns 'detailed information including full description and salary info', but does not disclose if it is read-only, authentication requirements, rate limits, or behavior on errors. Minimal disclosure beyond the tool's name.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that conveys the main purpose efficiently. No wasted words.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is minimally adequate but lacks details on return format, error handling, or what exactly constitutes 'detailed information'. It does not compensate for the absence of annotations.

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

Parameters3/5

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

Schema coverage is 100%: the only parameter 'jobUrl' is described as 'Full URL of the Behance job listing'. The description adds no additional meaning or context beyond what the schema already provides, so baseline score of 3 is appropriate.

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

Purpose5/5

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

Description clearly states it retrieves detailed information (full description and salary) for a specific Behance job listing. It uses a specific verb ('Get detailed information') and resource ('Behance job listing'), and distinguishes from sibling tools like get_behance_jobs which likely list jobs.

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

Usage Guidelines3/5

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

The description implies usage when a specific job URL is available, but does not explicitly state when to use or not use this tool, or mention alternatives like get_behance_jobs for listing jobs. Guidance is implied rather than explicit.

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

get_behance_jobsA

Get job listings from Behance. Returns job title, company, location, job type, posted date, required skills, and remote availability.

ParametersJSON Schema

Name	Required	Description
`category`	No	Filter by category (e.g., "Graphic Design", "UI/UX", "Illustration")
`location`	No	Filter by location (e.g., "New York", "London", "Remote")
`maxItems`	No	Maximum number of jobs to return (default: 50, max: 100)

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions returned fields but does not state if it's read-only, rate limits, pagination, or other side effects.

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

Conciseness5/5

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

Two concise sentences that front-load the purpose and list key fields. No unnecessary words.

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

Completeness3/5

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

No output schema, but description lists return fields. However, lacks details on filtering behavior, pagination, or error handling; adequate for a simple listing tool.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all parameters. The tool description adds no additional parameter meaning beyond the schema, achieving the baseline score.

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

Purpose5/5

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

The description clearly states the tool gets job listings from Behance and lists the specific fields returned (job title, company, etc.). It is distinct from sibling tools like get_behance_job_details or search_behance_projects.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The sibling names imply it's for listing jobs vs getting details, but the description doesn't clarify.

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

get_behance_profile_detailsB

Get detailed information about a specific Behance user profile including bio, company, occupation, social links, and complete stats.

ParametersJSON Schema

Name	Required	Description	Default
`profileUrl`	Yes	Full URL of the Behance profile

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions the type of data returned but does not state whether the operation is read-only, requires authentication, or how it handles errors (e.g., invalid URL, non-existent profile).

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

Conciseness5/5

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

A single, well-structured sentence that front-loads the purpose and lists key information included. No redundant words; every part earns its place.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is adequate but incomplete. It covers what data is returned but omits behavioral context (e.g., read-only nature, error handling, or typical response structure).

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

Parameters3/5

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

Schema description coverage is 100%; the parameter description ('Full URL of the Behance profile') is clear and matches the tool's purpose. The tool description adds no additional meaning beyond the schema, meeting the baseline expectation.

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

Purpose5/5

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

The description clearly states the tool retrieves detailed information about a specific Behance user profile, listing key fields like bio, company, occupation, social links, and stats. This distinguishes it from siblings like get_behance_project_details (different resource) and search_behance_profiles (search vs. retrieval).

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., search_behance_profiles). The description implies use when you have a profile URL, but does not state prerequisites or contrast with sibling tools.

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

get_behance_project_detailsA

Get detailed information about a specific Behance project including full description, all images, tags, and tools used.

ParametersJSON Schema

Name	Required	Description	Default
`projectUrl`	Yes	Full URL of the Behance project

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as read-only nature, authentication needs, rate limits, or potential side effects. The description only lists returned content but does not address tool behavior.

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

Conciseness5/5

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

The description is a single, clear sentence that front-loads the action and resource. Every word serves a purpose with no redundancy.

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

Completeness3/5

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

Given the absence of an output schema and annotations, the description provides a reasonable summary of return fields but lacks details on errors, limits, or other behavioral context. It is adequate for a simple tool but not comprehensive.

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

Parameters3/5

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

Schema coverage is 100% and the parameter 'projectUrl' is well-described in the schema. The description adds no additional meaning beyond what the schema provides, meeting the baseline for high coverage.

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

Purpose5/5

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

The description clearly states the action 'Get detailed information' and the resource 'specific Behance project', listing included details. It effectively distinguishes from sibling tools that deal with jobs, profiles, or search operations.

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

Usage Guidelines3/5

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

The description does not explicitly provide when-to-use or when-not-to-use guidance compared to alternatives. While the tool's purpose is clear, there is no mention of scenarios where search tools should be preferred or other context.

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

search_behance_imagesA

Search for images on Behance by keyword. Returns image URLs with dimensions, associated project info, and creator details.

ParametersJSON Schema

Name	Required	Description	Default
`keyword`	Yes	Search keyword (e.g., "logo design", "3d render", "photography")
`maxItems`	No	Maximum number of images to return (default: 50, max: 200)

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It states the return type but does not mention how results are sorted, whether pagination is used, or any rate limits. The behavior is adequately described for a search tool.

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

Conciseness5/5

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

The description is two sentences covering purpose and return content without any wasted words. It is front-loaded and efficient.

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

Completeness4/5

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

For a simple search tool with two parameters and no output schema, the description covers the main aspects: what it searches and what it returns. It could mention sorting or limitations, but overall it is sufficiently complete.

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

Parameters3/5

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

The input schema already describes both parameters with clear descriptions. The description adds no additional meaning beyond 'Search by keyword' and the schema's descriptions. With 100% schema coverage, baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool searches for images on Behance by keyword, and specifies the return includes URLs, dimensions, project info, and creator details. This distinguishes it from sibling tools that search for jobs, profiles, or projects.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives like search_behance_projects or search_behance_profiles. There is no mention of prerequisites or contexts where it is not appropriate.

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

search_behance_profilesA

Search for user profiles on Behance by keyword. Returns username, display name, avatar, location, followers, appreciations, and project count.

ParametersJSON Schema

Name	Required	Description	Default
`keyword`	Yes	Search keyword (e.g., "designer", "illustrator", agency name)
`maxItems`	No	Maximum number of profiles to return (default: 50, max: 200)

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool searches and returns specific fields, implying a read-only operation. However, it does not disclose behavioral traits such as authentication requirements, rate limits, pagination behavior, or any side effects.

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

Conciseness5/5

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

The description consists of two concise sentences. The first sentence states the purpose, and the second lists return fields. It is front-loaded and contains no unnecessary words.

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

Completeness3/5

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

Given no output schema and two parameters, the description covers purpose and return fields. However, it lacks details on pagination, ordering, and response structure, which are important for a search tool. The presence of sibling tools provides context but does not substitute for missing operational details.

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

Parameters3/5

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

Schema coverage is 100% with both parameters described. The description adds examples for the keyword parameter (e.g., 'designer') but does not significantly enhance understanding beyond the schema. The maxItems parameter is not elaborated beyond schema defaults.

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

Purpose5/5

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

The description clearly states the verb 'Search' and the resource 'user profiles on Behance by keyword'. It distinguishes this tool from siblings by specifying it returns user profile fields like username, display name, etc., while siblings like search_behance_projects and search_behance_images target different resources.

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

Usage Guidelines3/5

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

The description implies use for keyword-based profile search but does not explicitly contrast with other search tools (e.g., search_behance_projects, search_behance_images) or specify when not to use this tool. It lacks usage context like prerequisites or when to prefer this over get_behance_profile_details.

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

search_behance_projectsA

Search for projects on Behance by keyword. Returns project ID, title, URL, creator info, thumbnails, stats (views, appreciations, comments), and creative fields.

ParametersJSON Schema

Name	Required	Description	Default
`keyword`	Yes	Search keyword (e.g., "graphic design", "branding", "illustration")
`maxItems`	No	Maximum number of projects to return (default: 50, max: 200)

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It lists return fields but omits important traits such as rate limits, pagination behavior, default sorting, case sensitivity, or maximum result count beyond the maxItems parameter. This leaves significant gaps for an AI agent to infer safe and correct usage.

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

Conciseness5/5

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

The description is a single concise sentence that efficiently communicates the tool's purpose and output. No redundant or unnecessary information is present.

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

Completeness3/5

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

Given the absence of an output schema, the description helpfully enumerates return fields. However, it lacks details on pagination, sorting, error handling, and behavioral context (e.g., default limits, rate limiting). With only two parameters and full schema coverage, the description is partially complete but inadequate for a search tool in a production setting.

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

Parameters3/5

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

Input schema coverage is 100% with both parameters having descriptions. The tool description does not add any extra semantic detail beyond what the schema already provides. Baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb ('Search'), resource ('projects on Behance'), and mechanism ('by keyword'). It also lists specific return fields, effectively distinguishing it from sibling tools that target jobs, profiles, or specific project details.

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

Usage Guidelines3/5

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

The description implies usage for keyword-based project searches but does not explicitly state when to use this tool over alternatives like get_behance_project_details (for a specific project) or search_behance_images. No when-not-to-use guidance is provided.

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. Dates show when Glama detected each change.

7 tool updatesv1.0.0Jul 6, 2026
- First observedget_behance_job_details
- First observedget_behance_jobs
- First observedget_behance_profile_details
- First observedget_behance_project_details
- First observedsearch_behance_images
- First observedsearch_behance_profiles
- First observedsearch_behance_projects

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0

Disambiguation5/5

All tools have distinct purposes: job details vs list, profile details, project details, and separate searches for images, profiles, and projects. No overlap in functionality, so an agent can easily distinguish them.

Naming Consistency5/5

All tool names follow a consistent 'verb_behance_noun' pattern: get_behance_*_details, get_behance_*, search_behance_*. All lowercase with underscores, no mixed conventions.

Tool Count5/5

7 tools is appropriate for a read-only API covering profiles, projects, jobs, and image search. Not too few (covers main resources) nor too many (avoids bloat).

Completeness4/5

Covers search and detail retrieval for the main resource types. However, missing a direct tool to list projects by a specific user (only search by keyword). Minor gap but still functional for most use cases.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

HasDataOAuth
com.hasdata
All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.
Web Scraping Browser Automation
15
ReefAPI A
io.github.reefapi
One MCP server for 180+ live web-data APIs returning clean JSON from sites that block scrapers.
Web Scraping Browser Automation
523
luminati-io-brightdata-mcp
ai.smithery
One MCP for the Web. Easily search, crawl, navigate, and extract websites without getting blocked.…
Browser Automation Web Scraping Search
2
GTM API: LinkedIn MCP ServerOAuth
com.gtm-api
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.
Social Media Communication
1100

Related MCP Servers

crawl4ai-mcp
Web Scraping Agent Orchestration RAG Systems
ritvij14
F
license
B
quality
D
maintenance
An MCP Server for Web scraping and Crawling, built using Crawl4AI
Updated a year ago (2025-04-14 04:04 UTC)
2
24
-
LinkedIn MCP Server
Social Media Browser Automation
selvin-paul-raj
A
license
A
quality
D
maintenance
Fully featured MCP server that provides automation tools for LinkedIn, supporting browser-based scraping and API-based operations for content management, media uploads, and reactions.
Updated 3 months ago (2026-06-04 11:54 UTC)
6
3
MIT
scout-mcp-server
Browser Automation Web Scraping
stemado
A
license
A
quality
B
maintenance
MCP server for browser automation with anti-detection. Scout pages, find elements, interact with websites, and monitor network traffic from any AI client that supports the Model Context Protocol.
Updated 4 months ago (2026-05-20 13:17 UTC)
21
1
MIT
ScrapingBee MCP Server
Web Scraping Browser Automation
igormidev
A
license
Not graded
quality
D
maintenance
A Model Context Protocol (MCP) server that provides web scraping capabilities using the ScrapingBee API, allowing users to extract structured data from web pages using CSS/XPath selectors and other features.
Updated 9 months ago (2025-12-20 08:19 UTC)
15
1
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Arnonfr/behance-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

🔍 Behance MCP Server

✨ Features

🚀 Quick Start

Prerequisites

Installation

Alternative: Install via npx (Coming Soon)

⚙️ Configuration

Claude Desktop

Cursor

VS Code / GitHub Copilot

Kimi Code CLI

🛠️ Available Tools

1. search_behance_projects

2. get_behance_project_details

3. search_behance_profiles

4. get_behance_profile_details

5. search_behance_images

6. get_behance_jobs

7. get_behance_job_details

💡 Usage Examples

Search for branding projects:

Find designers in a location:

Get job listings:

Extract project details:

🏗️ Development

🧪 Testing

🔧 Troubleshooting

Browser not launching

Timeout errors

Memory issues

macOS permissions

💰 Pricing Comparison

📁 Project Structure

🤝 Contributing

Development Setup

📝 License

🙏 Acknowledgments

📧 Support

🔒 Security

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

1. `search_behance_projects`

2. `get_behance_project_details`

3. `search_behance_profiles`

4. `get_behance_profile_details`

5. `search_behance_images`

6. `get_behance_jobs`

7. `get_behance_job_details`