MCP server entry JSON ka chhota-sa tukda hai jiski failure berahem hai: koi key galat ho to error nahi aati, server bas dikhta nahi. Har transport ko alag aakaar chahiye — local ko command aur args, remote ko URL aur aam taur par ek header — aur inhe mila dene se aisi file banti hai jo poori dikhti hai aur kuchh karti nahi. Ye builder sirf wahi fields poochhta hai jinhe chuna hua transport sach mein use karta hai, doosre ka field bhara ho to warning deta hai, aur shayad vyavhaar ki sabse aam galti dikhata hai: aisi file mein asli credentials likh dena jo antatah repository mein jaati hai. Ye config file aur uske barabar ek-line command, dono deta hai.
Features
Sirf wo fields jo chuna hua transport use karta hai
Doosre transport ka field bhara ho to warning
File mein asli jaisa secret dikhe to chihnit, placeholder nahi
Remote host ke liye bina encryption HTTP par warning, localhost par chup
Server ka naam rakhiye — uske tools isi se grouped hote hain
Wo transport chuniye jo wo use karta hai
Command aur args bhariye, ya URL aur headers
JSON apne config mein copy kijiye, ya command chalaiye
Example
Input
"command": "npx -y some-server"
Output
Warning: looked up as a single executable with that name
Pehla shabd command hai; baaki sab args.
Common errors aur troubleshooting
Server kabhi dikhta hi nahi. — Aam taur par aakaar ki chook: url wali stdio entry, ya command wali remote entry. Dono yahaan dikhayi jaati hain, kyunki akele mein koi error nahi deti.
Command nahi milta. — Args alag rakhne hote hain. Command field mein npx aur baaki args list mein: space wala command usi naam ki ek executable ki tarah khoja jaata hai.
Mere yahaan chalta hai, doosron ke yahaan nahi. — Aam taur par args mein aapki machine ka poora path hai, ya aapke environment ke aise credentials chahiye jo kisi aur ke paas nahi.
Jo kuchh locally chalate hain uske liye stdio: client use process ki tarah shuru karta hai aur uske standard input-output se baat karta hai. Remote server ke liye HTTP. SSE mukhyatah un servers ke liye hai jo HTTP ke aam hone se pehle likhe gaye.
Config file kahaan jaati hai?
Project file repository mein rehti hai taaki poori team ko ek hi servers milein; desktop app ka apna config hai un servers ke liye jo aap har jagah chahte hain. Dono roop nikale jaate hain aur path dikhaya jaata hai.
Token file se bahar kaise rakhein?
Value ke bajaye environment variable ka reference likhiye. Yahaan ki jaanch dekhti hai ki value asli credential jaisa hai ya placeholder jaisa, aur sirf pehle par aapatti karti hai.
File lein ya command?
Dono ek hi kaam karte hain. Project ke saath version mein rakhna ho to file behtar; sirf aazma rahe hon to command tez. Dono ek hi fields se bante hain.
Server ka naam kyun maayne rakhta hai?
Yahi wo key hai jiske neeche entry rakhi jaati hai aur uske tools ka namespace bhi, isliye do servers ise share nahi kar sakte, aur naam badalne se har jagah un tools ka reference badal jaata hai.